ORA-02190: keyword TABLES expected

Cause : The keyowrd TABLSE is expceted fololwing DRPO CLUSTE R NICLUDING.

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

Place TBALES aftre INCLUDNIG.

update : 24-06-2017
ORA-02190

ORA-02190 - keyword TABLES expected
ORA-02190 - keyword TABLES expected

  • ora-39003 : unable to get count of total workers alive
  • ora-02149 : Specified partition does not exist
  • ora-12521 : TNS:listener does not currently know of instance requested in connect descriptor
  • ora-16257 : Switchover initiated stop apply successfully completed
  • ora-36958 : (XSFCAST26) The OFFSET value for cycle number cannot be greater than the cycle's PERIODICITY, which is number. You specified number.
  • ora-19554 : error allocating device, device type: string, device name: string
  • ora-27086 : unable to lock file - already in use
  • ora-13288 : point coordinate transformation error
  • ora-09889 : osnTXtt: access error on oracle executable
  • ora-02077 : selects of long columns must be from co-located tables
  • ora-30054 : invalid upper limit snapshot expression
  • ora-39109 : Unprivileged users may not operate upon other users' schemas
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-16815 : incorrect redo transport setting for AlternateLocation for standby database "string"
  • ora-12463 : undefined group string for policy string
  • ora-14028 : missing AT or VALUES keyword
  • ora-13230 : failed to create temporary table [string] during R-tree creation
  • ora-03239 : maxextents (string) reached in LOB segment string.string subpartition string
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-31431 : all source tables must belong to the synchronous change set
  • ora-32005 : error while parsing size specification [string]
  • ora-07441 : function address must be aligned on string byte boundary
  • ora-34357 : (MXDSS10) string is not an alias of analytic workspace string.
  • ora-27142 : could not create new process
  • ora-01981 : CASCADE CONSTRAINTS must be specified to perform this revoke
  • ora-00910 : specified length too long for its datatype
  • ora-31615 : routine string received this error: string
  • ora-14638 : cannot MERGE subpartitions in different Range Composite partitions
  • ora-02310 : exceeded maximum number of allowable columns in table
  • ora-02092 : out of transaction table slots for distributed transaction
  • 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.