This discussion is archived
0 Replies Latest reply: Aug 8, 2012 1:28 AM by BVV RSS

Error Importing Data for SY910

BVV Journeyer
Currently Being Moderated
Hi,

I am in a middle of upgrade process (9.0->9.1) and when I run ./InstallOracleDatabase.sh (previously modified ORCL_set.sh: RUN_MODE=UPGRADE) everything seems to go smooth and at the end I get:

--------------------------------------------------------------
- - - - - - - Start of loadall - - - - - - - - - - - - -

start of SHARED YES
--------------------------------------------------------------
Create and load SY910 tables

USER= SY910
LOAD_TYPE=SY
InstallOracleDatabase#
--------------------------------------------------------------
Data Load
User : SY910
Connect String : jdevm
Log File Directory : /u02/jdedwardsppack/e910/ORCL/logs
Frm User : SY910
Load Type : SY -- dta, ctl, dd, ol, sy
Please Review Logs for Errors
--------------------------------------------------------------


Tue Aug 7 13:53:35 CEST 2012

Importing SY Data for SY910
--
-- First create dump directory
--
ERROR:
ORA-01017: invalid username/password; logon denied


SP2-0751: Unable to connect to Oracle. Exiting SQL*Plus
--
-- Now turn off logging at TBSP level
--
old 1: alter tablespace &&OWNER.t NOLOGGING
new 1: alter tablespace SY910t NOLOGGING

Tablespace altered.

old 1: alter tablespace &&OWNER.i NOLOGGING
new 1: alter tablespace SY910i NOLOGGING

Tablespace altered.


Import: Release 11.2.0.1.0 - Production on Tue Aug 7 13:53:38 2012

Copyright (coffee) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

UDI-01017: operation generated ORACLE error 1017
ORA-01017: invalid username/password; logon denied

Username: system
Password:

UDI-12162: operation generated ORACLE error 12162
ORA-12162: TNS:net service name is incorrectly specified

--
-- Now turn on logging at TBSP level
--
old 1: alter tablespace &&OWNER.t LOGGING
new 1: alter tablespace SY910t LOGGING

Tablespace altered.

old 1: alter tablespace &&OWNER.i LOGGING
new 1: alter tablespace SY910i LOGGING

Tablespace altered.

[oracle@e1db ORCL]$


and when it asked me for username I provided the DB system user and password. Maybe here was a mistake but all usernames and passwords are hardcoded in ORCL_set.sh file...

Have you encountered something like this? How can I overrun it? Can I start this script again? I can see that I have the schemas created in DB but no tables inside.

BVV

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points