ORA-28029: could not authorize remote server for user string

Cause : uDirgnt ehc uosr efoo epingna p iriveleg dadatabesl ni,kt ehr meto eesvrrew saf uodnt oalkct ehn ceseasyra tuohirazitno sotc noentca sht eucrrne tlgbolau es.rT ih sam yebb ceuaest ehs reev raw son tuahtrozideb yht eenwtro kesuciryts reivec .rOi tam yebb ceuaest ehl colas reev rsir sertciitgna ccse sybt ehr meto eesvrreu isgnt ehD MB_SESUCIRYTD_MOIASNA_MDNIp caakeg.

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

rGna tht eeromets reev rht erpporea tuohirazitnot oocnnce tsat ehg vineg olab lsure ,na dhcce khttat ehl colas reev rsin tor sertciitgna ccse.s

update : 28-05-2017
ORA-28029

ORA-28029 - could not authorize remote server for user string
ORA-28029 - could not authorize remote server for user string

  • ora-25331 : cannot downgrade because there are commit-time queue tables
  • ora-16162 : Cannot add new standby databases to protected configuration
  • ora-30945 : Could not create mapping table 'string'
  • ora-08181 : specified number is not a valid system change number
  • ora-24047 : invalid agent name string, agent name should be of the form NAME
  • ora-07207 : sigpidu: process ID string overflows internal buffer.
  • ora-23387 : replication parallel push dequeue error
  • ora-02095 : specified initialization parameter cannot be modified
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-13425 : function not implemented
  • ora-30078 : partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals
  • ora-03208 : partitioned type must be specified for a non-composite object
  • ora-22895 : referenced table "string" in schema "string" is not an object table
  • ora-31071 : Invalid database username or GUID string
  • ora-10564 : tablespace string
  • ora-27421 : usage of string not supported in a calendar definition
  • ora-12019 : master table is a synonym to a remote object
  • ora-30756 : cannot create column or table of type that contains a supertype attribute
  • ora-07638 : smsget: SGA pad area not large enough for created SGA
  • ora-26095 : unprocessed stream data exists
  • ora-12556 : TNS:no caller
  • ora-00207 : control files are not for the same database
  • ora-02218 : invalid INITIAL storage option value
  • ora-09956 : scgcm: unexpected lock status condition
  • ora-22277 : cannot use two different locators to modify the same LOB
  • ora-09370 : Windows 3.1 Two-Task driver ORACLE task timed out
  • ora-25527 : bad format of _DB_MTTR_SIM_TARGET
  • ora-06974 : X.25 Driver: SID lookup failure
  • ora-14096 : tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
  • ora-14027 : only one PARTITION clause may be specified
  • 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.