Submitted by Hunter T Tweed on Sep 7, 2010 7:22:32 AM

Steps to update Portal database connection information after completing database-transfer

Also to be clear** I meant a supported method of automatically renaming the schema with Portal scripts.

Submitted by Hunter T Tweed on Sep 7, 2010 7:21:19 AM

Steps to update Portal database connection information after completing database-transfer

This script only updates the connection information...it does not touch anything within the database itself. I will make that clearer in the 'about the script' section.

I am not aware of a supported method of renaming the schema in a Portal database short of actually re-transferring the data to a brand new database with a new schema. Or you could do the following process:

- Manually rename all of the schema objects

- Execute 'connect-database' to update the Portal configuration with the new schema name

Submitted by Micheal Choi on Sep 7, 2010 12:33:31 AM

Steps to update Portal database connection information after completing database-transfer

After jcr schema name is renamed, the above procedure does not seem to update the 17 views of jcr such as ICMSTJCRLV00001, and I had to update it manually with something like:

create or replace view icmadmin_new.ICMSTJCRLV00001 (WSID,LID, TNSID, TNAME, SIID, TIID, TCTID, TACLCODE, TIX, SVID, TVID,STATUS,UCTNAME, LINKFLAG, INLEAFTREEFLAG) as SELECT 1, LID, TNSID, TNAME, SIID, TIID, TCTID, TACLCODE, TIX, SVID, TVID, 0, UCTNAME, LINKFLAG, INLEAFTREEFLAG FROM icmadmin_new.ICMSTJCRLINKS WHERE WSID=1;

Is there any better way to do it? I saw it from database-transfer that it drops the view and re-creates it, but evidently the connect-database does not have this - at least it is so at version 6.0.1.3.