I've always used / as sysdba, but using system gets the same result.
I'm starting to lean towards a bug introduced in the October PSU, since that's
the only change since the last time I ran this.
Scott Canaan '88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco@xxxxxxx<mailto:srcdco@xxxxxxx> | c: (585) 339-8659
CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.
From: Sweetser, Joe [mailto:JSweetser@xxxxxxxx]
Sent: Tuesday, March 05, 2019 8:53 AM
To: Scott Canaan; oracle-l@xxxxxxxxxxxxx
Subject: RE: Oracle impdp Issue
Could the issue/difference be using / as sysdba?
From here:
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/sutil/datapump-import-utility.html#GUID-D34AA2AC-DD27-4557-98AC-CE9A3AC21E35
This: Do not start Import as SYSDBA, except at the request of Oracle technical
support. SYSDBA is used internally and has specialized functions; its behavior
is not the same as for general users.
Maybe try it as system or some other user with the appropriate privs?
Hth,
-joe
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Scott Canaan
Sent: Tuesday, March 5, 2019 6:46 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Oracle impdp Issue
I'm trying to do a network import using impdp. I've done this at least 100
times and only run into this issue once before.
oracle@clawstgea2:CLAWSTGA>k=old_clawstga.rit.edu<mailto:oracle@clawstgea2:CLAWSTGA%3ek=old_clawstga.rit.edu>
parallel=4 <
Import: Release 12.1.0.2.0 - Production on Tue Mar 5 08:29:44 2019
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
Username: / as sysdba
Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit
Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing
options
ORA-39006: internal error
ORA-39113: Unable to determine database version
ORA-06550: line 1, column 7:
PLS-00352: Unable to access another database 'OLD_CLAWSTGA.RIT.EDU'
ORA-06550: line 1, column 7:
PLS-00201: identifier 'SYS@OLD_CLAWSTGA.RIT.EDU' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
ORA-39097: Data Pump job encountered unexpected error -6550
I've double-checked that the database link is public and connects to system.
It works:
SQL> select name, created from v$database@old_clawstga;
NAME CREATED
--------- ---------
CLAWSTGA 27-FEB-14
GLOBAL_NAMES is FALSE on both databases.
The last time I had this problem, it was fixed by setting streams_pool_size to
0. Both databases have that set to 0 already.
I did run this successfully on this database back in December, so the only
thing that's changed since then is the October PSU that was installed in
January.
I've had a hard time getting this scheduled with the customer, so I have to
find a way to get it done today. Any help will be greatly appreciated.
Thank you,
Scott Canaan '88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco@xxxxxxx<mailto:srcdco@xxxxxxx> | c: (585) 339-8659
CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.
This e-mail transmission and any attachments that accompany it may contain
information that is privileged, confidential or otherwise exempt from
disclosure under applicable law and is intended solely for the use of the
individual's to whom it was intended to be addressed. If you have received this
e-mail by mistake, or you are not the intended recipient, any disclosure,
dissemination, distribution, copying or other use or retention of this
communication or its substance is prohibited. If you have received this
communication in error, please immediately reply to the author via e-mail that
you received this message by mistake and also permanently delete the original
and all copies of this e-mail and any attachments from your computer. Please
note that coverage cannot be bound or altered by sending an email. You must
receive written confirmation from a representative of our firm to put coverage
in force or make changes to an existing policy.
