adop_20170116_122044.log
Comments
-
Hello,
Can you try to bounce the DB Services and check if the issue surfaces.
Regards,
Narsi
2 -
Hello,
Can you try to bounce the DB Services and check if the issue surfaces.
Regards,
Narsi
I'll try that.
Other this is that :
When I log into patch file system - I am unable to connect to apps user in sqlplus i get the below error :
[appldev@papebsorat01 ebsdev]$ sqlplus apps
SQL*Plus: Release 10.1.0.5.0 - Production on Mon Jan 16 14:18:10 2017
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-00068: invalid value 600 for parameter ddl_lock_timeout, must be between
18446744071751663422 and 18446744071751397461
ORA-06512: at line 26
But I am able to connect to system within same session :
Enter user-name: system
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL>
Recently I have cloned the env from Production and ran fs_clone with success.
Regards,
Harmeet Luthra
0 -
I'll try that.
Other this is that :
When I log into patch file system - I am unable to connect to apps user in sqlplus i get the below error :
[appldev@papebsorat01 ebsdev]$ sqlplus apps
SQL*Plus: Release 10.1.0.5.0 - Production on Mon Jan 16 14:18:10 2017
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-00068: invalid value 600 for parameter ddl_lock_timeout, must be between
18446744071751663422 and 18446744071751397461
ORA-06512: at line 26
But I am able to connect to system within same session :
Enter user-name: system
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL>
Recently I have cloned the env from Production and ran fs_clone with success.
Regards,
Harmeet Luthra
HI,
Can you confirm the value which has been set for the below parameter.
show parameter ddl_lock_timeout
You can give atry by setting the following.
set timing on
alter session set ddl_lock_timeout=0
The default value of zero indicates a status of NOWAIT.
Regards,
Balaji
0 -
Hello,
Can you try to bounce the DB Services and check if the issue surfaces.
Regards,
Narsi
Bouncing the database has resolved the issue.
0