[cspadola]

I now get as far as creating the reportowner grants. In the next step, it tells me to create the public synonyms (connected as REPORTOWNER). When I run this script, I get the following error:

SQL> @create_public_synonyms
SELECT owner, table_owner FROM DBA_SYNONYMS WHERE SYNONYM_NAME = p_synonym_name;
*
ERROR at line 8:
ORA-06550: line 8, column 35:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 8, column 4:
PL/SQL: SQL Statement ignored

In the previous step I was able to run this error-free when connacted as GLOGOWNER. When I check in each of the GLOGOWNER and REPORTOWNER instances, I see that PUBLIC.DBA_SYNONYMS exist.

Up until this step, all other scripts ran error-free.

[nick.polites]

You probably have an error in the import. Post the import log file and I'll see if I can help.

[cspadola]

Hi Nick...I have zipped up the import log file and attached it here. I see that there are a lot of errors but I assumed that this is because I was importing (again) and that the errors are caused by a table or object that already exists. But then again, I could be way off.

Thanks for your help.

[nick.polites]

You need to run the create_glog_roles.sql and create_glog_users.sql scripts. This will wipe out all of the data in the database to ensure a clean import. You may get some IMP errors at the end of the import but you can ignore those. If you get any errors while the tables are importing that is bad and needs to be addressed.

Try it again and you should be good to go.

[nick.polites]

Oh and one other thing:

ORA-01658: unable to create INITIAL extent for segment in tablespace INDX


You ran out of tablespace for the INDX datafile. Make sure you have these set to autoextend on or make them large enough to import the database. You need at least 5 gigs to the INDX and DATA tablespaces on a GA import. It will be higher if you are copying from a production instance.

[cspadola]

Hi Nick...when I ran the script create_gc3_tablespaces, I told it to Autoextend when it prompted me for that. Meaning, I put a 'Y' at that prompt.

Is this sufficient?

[cspadola]

However, that said, I see that the MAX_EXTENTS for tablespace INDX is 2147483645.

[nick.polites]

I think there was a bug in the script and it never took it. When it asks you to create it now, I always said no so that I could see all of the parameters. In any case, you can log into the Oracle Enterprise Manager (oemapp dbastuido from sqlplus, not on the db) and adjust this as needed, or use Toad.

[cspadola]

Hi Nick...I dropped all the tablespaces and tried to recreate them after I modified the create_tablespace_package file to allow up to 6048000K max file size. However, this resulted in errors when I tried to run the create_gc3_tablespaces script again. I ran the create_gc3_tablespaces script again after reverting back to the original create_tablespace_package file with the 2048000K max file size. It worked without errors but now I need to manually extend the max size on the INDX and DATA tablespaces as you recommended.

I am unable to get Enterprise Manager console up and running. Is this still available? Otherwise, can you tell me the sql command to alter the tablespace max size from the current 2GB size to the 5GB size you suggested?

[nick.polites]

Not sure why you were getting an error. Here is what the tablespaces should look like to get autoextend on.

CREATE TABLESPACE DATA
DATAFILE '/u01/app/oracle/database/OTM/DATA01.dbf'
SIZE 1024000K REUSE
AUTOEXTEND ON NEXT 1024000K MAXSIZE UNLIMITED
SEGMENT SPACE MANAGEMENT AUTO EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M
/

CREATE TABLESPACE INDX
DATAFILE '/u01/app/oracle/database/OTM/INDX01.dbf'
SIZE 1024000K REUSE
AUTOEXTEND ON NEXT 1024000K MAXSIZE UNLIMITED
SEGMENT SPACE MANAGEMENT AUTO EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M
/

I don't know the commands offhand but check on google for how to increase tablespace sizes and alter the tablespaces to allow autoextend on.