ORA-25235: fetched all messages in current transaction

Cause : The NEXT_TRANSACTION navigation option was used in a dequeue when there were no more messages that belong to the same transaction.

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

Use the NEXT_TRANSACTION navigation option to move to the next also use the FIRST_MESSAGE option to start from the head of the queue again.

update : 29-06-2017

ORA-25235 - fetched all messages in current transaction
ORA-25235 - fetched all messages in current transaction

  • ora-12084 : must use ALTER MATERIALIZED VIEW to alter "string"."string"
  • ora-16723 : setting AlternateLocation property conflicts with the redo transport setting
  • ora-07704 : error in archive text: need ':' after device name
  • ora-01921 : role name 'string' conflicts with another user or role name
  • ora-01671 : control file is a backup, cannot make a standby control file
  • ora-38854 : cannot mark instance string (redo thread string) as disabled
  • ora-15031 : disk specification 'string' matches no disks
  • ora-00297 : must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START
  • ora-14623 : Value string does not exist in subpartition string
  • ora-06405 : NETCMN: reset protocol error
  • ora-01569 : data file too small for system dictionary tables
  • ora-08452 : specification of E in picture mask is unsupported
  • ora-19659 : incremental restore would advance file string past resetlogs
  • ora-31410 : change set string is not an existing change set
  • ora-09890 : osnTXtt: malloc failed
  • ora-15150 : instance lock mode 'string' conflicts with other ASM instance(s)
  • ora-02708 : osnrntab: connect to host failed, unknown ORACLE_SID
  • ora-38609 : FI Not enough memory for tree counting, requires at least stringKB
  • ora-29504 : invalid or missing schema name
  • ora-06547 : RETURNING clause must be used with INSERT, UPDATE, or DELETE statements
  • ora-37073 : (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
  • ora-07444 : function address string is not readable
  • ora-38772 : cannot add datafile 'string' - file could not be created
  • ora-30945 : Could not create mapping table 'string'
  • ora-37006 : (AWLISTALL04) number writers
  • ora-06140 : NETTCP: no such user
  • ora-16629 : database reports a different protection level from the protection mode
  • ora-01093 : ALTER DATABASE CLOSE only permitted with no sessions connected
  • ora-21709 : cannot refresh an object that has been modified
  • ora-19813 : cannot have unavailable file string in DB_RECOVERY_FILE_DEST
  • 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.