Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 
 

ORA-38500: %s

Oracle Tips by Burleson Consulting
December 8,  2008

 

The documentation notes the following about ORA-38500:

ORA-38500: %s

Cause: There was a generic error

Action: See documentation for further information.

The Oracle documentation above on ORA-38500 is obviously a little mysterious.  This being said, when encountering ORA-38500, it is important to look into all possible causes and aggressively evaluate all processes and attached errors and title. 

For example, on Oracle DBA Forums, a user has experienced ORA-38500 in this context: 

I am on 10gR2.  I want to implement real time application of redo logs on my physical standby db.  I issued the following command but it failed and gave ORA-38500.

SQL> alter database recover managed standby database using current logfile;
alter database recover managed standby database using current logfile
*
ERROR at line 1:
ORA-38500: USING CURRENT LOGFILE option not available without stand
 

To resolve this instance of ORA-38500, the user was advised that needed "standby redologs on the standby databse in order to use redo apply OR sql apply using the current logfile.”

From: http://dbaforums.org/oracle/lofiversion/index.php?t8525.html


Oracle MOSC also has information on ORA-38500 involving a bug.  The article, Bug 6708565 - DBMS_RLMGR fails with ORA-38500 when specifying NLS length semantic, should be good to check out if you think this might be the reson for your occurance of ORA-38500.  Here is some of the documentation to help you decide:

An attempt to create a rule class with attributes or action preferences configured with a VARCHAR2 data type with specific length semantic (eg: as in VARCHAR2(10 CHAR) ), fails with an invalid data type error. 

Workaround:
Use VARCHAR2 data type without specific length semantics.

 


 

 

��  
 
 

 
 
 
 
oracle dba poster
 

 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright ? 1996 -  2014

All rights reserved by Burleson

Oracle ? is the registered trademark of Oracle Corporation.