Got this error.
Try to connect your database server directly.Definitely you will get this error.
Enter user-name: sys as sysdba
Enter password:
ERROR:
ORA-00020: maximum number of processes (250) exceeded
you need to down your listener
Try to login directly using sqlplus
If that not possible
Then ... shutdown your db service
After that increase your number of processes
by
SQL>ALTER SYSTEM SET PROCESSES=350 SCOPE=SPFILE;
you must shutdown after this commands for changing this parameter.
Monday, June 6, 2011
Wednesday, June 1, 2011
kewastUnPackStats(): bad magic 1 (0x2b2b8f4652ad, 0)
Found the error in rdbms alert log...?
It generates thousands of lines per day which will expand the alert log size.
We can override this error by
ALTER SYSTEM SET control_management_pack_access='NONE' SCOPE=MEMORY;
Otherwise we can download new patches from Metalink.
Cheers...!!!
It generates thousands of lines per day which will expand the alert log size.
We can override this error by
ALTER SYSTEM SET control_management_pack_access='NONE' SCOPE=MEMORY;
Otherwise we can download new patches from Metalink.
Cheers...!!!
Friday, May 27, 2011
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENER_ORA11G'
you need to check your tnsnames.ora file.In this above example.You can see "LISTENER_ORA11G" that is actually a service name from tnsnames.ora file.Check that service name configuration in tnsnames.ora.
Cheers.!!!
ORA-00132: syntax error or unresolved network name 'LISTENER_ORA11G'
you need to check your tnsnames.ora file.In this above example.You can see "LISTENER_ORA11G" that is actually a service name from tnsnames.ora file.Check that service name configuration in tnsnames.ora.
Cheers.!!!
Friday, May 20, 2011
ORA-00845: MEMORY_TARGET not supported on this system
Got this error...?
This type of error depends on your server memory allocated to your database.You need to change your memory_target.
Alter system set memory_target= 2000M scope=both;
cheers!!!
This type of error depends on your server memory allocated to your database.You need to change your memory_target.
Alter system set memory_target= 2000M scope=both;
cheers!!!
Monday, May 9, 2011
The OracleDBConsolev8it3 service terminated with service-specific error 1 (0x1).
Got this error?
The OracleDBConsolev8it3 service terminated with service-specific error 1 (0x1).
emca -config dbcontrol db
SEVERE: Failed to unlock all EM-related accounts
Could not complete the configuration. Refer to the log file for more details
It`s a common error. you need to drop dbconsole first.after that you can recreate the same
1)DROP DBCONSOLE first
emca -deconfig dbcontrol db -repos drop
then
2)CREATE NEW REPOSITORY
emca -repos create
emca -config dbcontrol db
It will take sometime to create new repository.Also you can see the path of EM at end of the execution.
Restart EM Console
emctl stop dbconsole db
emctl start dbconsole db
Cheers!!!
The OracleDBConsolev8it3 service terminated with service-specific error 1 (0x1).
emca -config dbcontrol db
SEVERE: Failed to unlock all EM-related accounts
Could not complete the configuration. Refer to the log file for more details
It`s a common error. you need to drop dbconsole first.after that you can recreate the same
1)DROP DBCONSOLE first
emca -deconfig dbcontrol db -repos drop
then
2)CREATE NEW REPOSITORY
emca -repos create
emca -config dbcontrol db
It will take sometime to create new repository.Also you can see the path of EM at end of the execution.
Restart EM Console
emctl stop dbconsole db
emctl start dbconsole db
Cheers!!!
Thursday, April 21, 2011
Unable to open Log File-EXPDP & IMPDP error
ORA-39002
ORA-39070
ORA-29283
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283
Check out expdp with default directory.If this ok.Then check out drive security.There is no SYSTEM user in SECURITY Tab.Add system user to SECURITY.Then try.
Cheers!!!
ORA-39070
ORA-29283
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283
Check out expdp with default directory.If this ok.Then check out drive security.There is no SYSTEM user in SECURITY Tab.Add system user to SECURITY.Then try.
Cheers!!!
Tuesday, April 5, 2011
ORA-01000 maximum open cursors exceeded
Cause: A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user.
Action: Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.
ALTER SYSTEM SET open_cursors = 400 SCOPE=BOTH;
Try to find out application to see why cursors are staying open.
Action: Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.
ALTER SYSTEM SET open_cursors = 400 SCOPE=BOTH;
Try to find out application to see why cursors are staying open.
Subscribe to:
Posts (Atom)