cancel
Showing results for 
Search instead for 
Did you mean: 

ORADBUSR.SQL error ORA-03114: not connected to ORACLE

Former Member
0 Kudos

Hi,

I'm refreshing an Oracle 10 database and hitting a snag running oradbusr.sql. It appears to be execute at least parts of the sql script and then abend, with an ORA-03114.

The problem I'm hitting is the bulk of the PL/SQL is within a block. It appears dbms_output will only print at the end of the block, which it doesn't reach. prompt and print don't seem to be the answer either.

Has anyone hit this problem? Does anyone have suggestions on how to diagnose where it's failing?

Best regards,

Russ

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

I reinstalled Oracle, which corrected all issues.

Former Member
0 Kudos

Hi,

Thanks for the response. No, /etc/hosts and DNS look good and appear to be working fine.

Best regards,

Russ

Former Member
0 Kudos

Nope, I ran the cat scripts. And I cannot rerun them as they contain sql that attempts to do grants on synonyms, so they would blow up the same was as the original problem.

Thanks anyway.

Best regards,

Russ

former_member204746
Active Contributor
0 Kudos

check the last 2 posts from

Former Member
0 Kudos

Hi,

Thanks for the response. The alert log was a great suggestion. Here's the output of the script:

SQL*Plus: Release 10.2.0.4.0 - Production on Wed Jun 2 12:30:03 2010

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected.

old 6: if length('&&1') = 5 then

new 6: if length('SAPSR3') = 5 then

old 7: if substr(upper('&&1'),1,5) = 'SAPR3' then

new 7: if substr(upper('SAPSR3'),1,5) = 'SAPR3' then

old 11: if upper('&&2') = 'NT' then

new 11: if upper('UNIX') = 'NT' then

old 18: :sDomain := upper('&&3');

new 18: :sDomain := upper('SM1');

old 19: :sSapSid := upper('&&4');

new 19: :sSapSid := upper('x');

old 21: :sSapSid := upper('&&3');

new 21: :sSapSid := upper('SM1');

old 37: :sSchema := upper('&&1');

new 37: :sSchema := upper('SAPSR3');

old 39: if upper('&&2') = 'NT' then

new 39: if upper('UNIX') = 'NT' then

old 46: :sDomain := upper('&&3');

new 46: :sDomain := upper('SM1');

old 47: :sSapSid := upper('&&4');

new 47: :sSapSid := upper('x');

old 49: :sSapSid := upper('&&3');

new 49: :sSapSid := upper('SM1');

using following Parameters:

.

. Oracle Version: 10.2.0.4.0

. Parametervalue os_authent_prefix: OPS$

. Schema Id: SR3

. Database User (Schema): SAPSR3

. SAP R/3 Administrator: OPS$SM1ADM

. SAP R/3 Serviceuser: OPS$SAPSERVICESM1

.

ERROR:

ORA-03114: not connected to ORACLE

Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

With the Partitioning, Data Mining and Real Application Testing options

Here's an excerpt from a trace file referenced in the alert log

      • 2010-06-02 12:30:04.289

ksedmp: internal or fatal error

ORA-07445: exception encountered: core dump [lxhh2ci] [SIGSEGV] [Address not mapped to object] [0xD574538454243A0] [] []

Current SQL statement for this session:

grant select on sap$histgrm to public

-


PL/SQL Call Stack -


The script was blowing up granting select on the synonym:

grant select on sap$histgrm to public

I changed the statement to grant select on the view and it worked fine.

grant select on sap_$histgrm to public

The problem is it almost immediately hits sappost.sql which has additional grants on synonyms, which for some reason don't work.

Best regards,

Russ

former_member204746
Active Contributor
0 Kudos

Russ,

please search Google with these keywords:

lxhh2ci SIGSEGV

it seems you forgot to run cat* scripts

fjhernanz
Contributor
0 Kudos

Hi,

ORA-3114 is just a secondary error. Please paste the output of the script, is there any other ORA error with it? check the alertlog as well.

Br,

Javier