ORA-36863: (XSTFRC03) The OLAPRC_TABLE function encountered an error while parsing the COLUMNMAP.

Cause : Invalid COLUMNMAP syntax.

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

Check the syntax of the column map. Normally, users should not call OLAP Random Access Cursor table function themselves and therefore should not encounter this error.

update : 29-06-2017

ORA-36863 - (XSTFRC03) The OLAPRC_TABLE function encountered an error while parsing the COLUMNMAP.
ORA-36863 - (XSTFRC03) The OLAPRC_TABLE function encountered an error while parsing the COLUMNMAP.

  • ora-00365 : the specified log is not the correct next log
  • ora-02277 : invalid sequence name
  • ora-12438 : repeated policy option: string
  • ora-15069 : ASM file 'string' not accessible; timed out waiting for lock
  • ora-31167 : XML nodes over 64K in size cannot be inserted
  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-16232 : adding Logical Standby skip entry for table string.string
  • ora-36639 : (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number.
  • ora-06420 : NETCMN: SID lookup failure
  • ora-02794 : Client unable to get key for shared memory
  • ora-27038 : created file already exists
  • ora-26506 : null global context
  • ora-32830 : result code string returned by Messaging Gateway agent
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-25157 : Specified block size string is not valid
  • ora-28104 : input value for string is not valid
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-14460 : only one COMPRESS or NOCOMPRESS clause may be specified
  • ora-38305 : object not in RECYCLE BIN
  • ora-01255 : cannot shutdown - file string in recovery manager backup
  • ora-10582 : The control file is not a backup control file
  • ora-02439 : Unique index on a deferrable constraint is not allowed
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-12440 : insufficient authorization for the SYSDBA package
  • ora-19663 : cannot apply current offline range to datafile string
  • ora-01505 : error in adding log files
  • ora-12683 : encryption/crypto-checksumming: no Diffie-Hellman seed
  • ora-32817 : message system link string is not configured with a log queue for string
  • 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.