ORA-02178: correct syntax is: SET TRANSACTION READ { ONLY | WRITE }

Cause : There is a syntax error in the user's statement.

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

Correct the syntax as indicated.

update : 24-08-2017
ORA-02178

ORA-02178 - correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
ORA-02178 - correct syntax is: SET TRANSACTION READ { ONLY | WRITE }

  • ora-07202 : sltln: invalid parameter to sltln.
  • ora-02150 : invalid new tablespace name
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-03205 : partition name is required when partitioned type is specified
  • ora-26088 : scalar column "string" must be specified prior to LOB columns
  • ora-29275 : partial multibyte character
  • ora-02212 : duplicate PCTFREE option specification
  • ora-25209 : invalid value string, EXPIRATION should be non-negative or NEVER
  • ora-01298 : conflicting dictionary option
  • ora-12596 : TNS:internal inconsistency
  • ora-13138 : could not determine name of object string
  • ora-26006 : Incorrect bind variable in column string's sql expression - string
  • ora-32614 : illegal MODEL SELECT expression
  • ora-26052 : Unsupported type number for SQL expression on column string.
  • ora-36608 : (XSAGHOVERFLOW) The depth of the hierarchies encountered while processing a composite dimension in AGGREGATE caused a counter overflow.
  • ora-09751 : pw_attachPorts: server call pws_attach failed.
  • ora-26018 : Column string in table string does not exist
  • ora-01648 : log string is the current log of disabled instance string (thread string)
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-16520 : unable to allocate resource id
  • ora-26521 : rpc initialization error
  • ora-09200 : sfccf: error creating file
  • ora-14503 : only one partition name can be specified
  • ora-24952 : register, unregister or post has incorrect collection count
  • ora-37001 : You have one or more attached but unupdated analytic workspaces.
  • ora-36991 : (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.
  • ora-01290 : cannot remove unlisted logfile string
  • ora-36995 : (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
  • ora-32814 : propagation schedule string does not exist
  • ora-28335 : referenced or referencing FK constraint column cannot be encrypted
  • 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.