ORA-28561: unable to set date format on non-Oracle system

Cause : Initilaizatino of aH eteroegneousS ervicse conncetion ot set hte dat eforma tto beu sed o nthe cnonecte dnon-Oarcle ssytem.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

If th eOracl edata idctionray suplpies av alue ofr theH S_NLSD_ATE_FROMAT praamete,r confrim tha tthis avlue i sformatted correctlyb y ther ules fo the onn-Oralce sysetm. Alos chec kfor additionla infomrationi n loga nd trcae filse genearted b ythe Hteerogeenous Srevicesa gent.

update : 29-04-2017

ORA-28561 - unable to set date format on non-Oracle system
ORA-28561 - unable to set date format on non-Oracle system

  • ora-39092 : unable to set SCN metadata for object "string.string" of type string
  • ora-00238 : operation would reuse a filename that is part of the database
  • ora-24041 : propagation schedule exists for QUEUE string and DESTINATION string
  • ora-09859 : sfngat: the input file name is not in the autobackup OMF format
  • ora-19640 : datafile checkpoint is SCN string time string
  • ora-38438 : getVarchar not possible due to "string" datatype in the attribute set
  • ora-02875 : smpini: Unable to get shared memory for PGA
  • ora-23379 : connection qualifier "string" is too long
  • ora-25302 : Operation not possible for non-buffered queue string
  • ora-09745 : smscre: vm_allocate error, unable to create shared memory.
  • ora-14054 : invalid ALTER TABLE TRUNCATE PARTITION option
  • ora-30387 : invalid rewrite mode for REWRITE_EQUIVALENCE API
  • ora-31512 : name cannot contain double quotation marks
  • ora-14194 : only one subpartition may be rebuilt
  • ora-01326 : compatability of 9.0 or greater required to build into the logstream
  • ora-10561 : block type 'string', data object# string
  • ora-38748 : cannot flashback data file string - file is in use or recovery
  • ora-19017 : Attributes can only be simple scalars
  • ora-16764 : redo transport service to a standby database is offline
  • ora-37133 : (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.
  • ora-19101 : CONTENT keyword expected
  • ora-16786 : resource guard cannot access Data Guard broker metadata
  • ora-31431 : all source tables must belong to the synchronous change set
  • ora-38713 : Flashback Database logging is already turned on.
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-24144 : rules engine internal error, arguments: [string], [string]
  • ora-39004 : invalid state
  • ora-31627 : API call succeeded but more information is available
  • ora-19162 : XP0004 - XQuery type mismatch: invalid argument types 'string', 'string' for function 'string'
  • ora-09815 : File name buffer overflow
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.