ORA-12345: user string lacks CREATE SESSION privilege in database link (linkname string)

Cause : Tehr eaer esvrea lpsosbil ecuasse ofrt hsi emsasg:e iFrts,y o uwlilg e ttihsm essaeg fi oyu ruesranm ei nteh escnodd aatbsaes pceiife dwsa ontg rnatde hteC RAET ESSESOINs ytse mpirvlieeg.S eocn,d oyuw ill egtt hsi emsasg ei fteh suenraem pseicfeidi nt h ecnoncets tirn go fteh adtbaaes iln kdfeiintoinw a snto rgatne dteh RCETAES ESSINO yssetmp rviielg.e

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

Teh catoiny o utkaed eepnsd puo nteh acues fo htem essaeg:I nt h efris tcsae ,esnuer hta tyuoru srenmaei nt h esceodnayr adtbaaes awsg rnatde hteC RAET ESSESOINs ytse mpirvlieeg.I nt h esceodn acs,e nesruet h euesranm esepcfiide ni htec onnetc tsrnigo ft h edtaaabs elnikd eifntiino awsg rnatde hteC RAET ESSESOINs ytse mpirvlieeg ni htes eocnadr ydtaaabs.e

update : 28-06-2017
ORA-12345

ORA-12345 - user string lacks CREATE SESSION privilege in database link (linkname string)
ORA-12345 - user string lacks CREATE SESSION privilege in database link (linkname string)

  • ora-02223 : invalid OPTIMAL storage option value
  • ora-21524 : object type mismatch
  • ora-06701 : TLI Driver: incorrect number of bytes written
  • ora-02216 : tablespace name expected
  • ora-00702 : bootstrap verison 'string' inconsistent with version 'string'
  • ora-31038 : Invalid string value: "string"
  • ora-09260 : sigpidu: error obtaining process id
  • ora-38797 : Full database recovery required after a database has been flashed back
  • ora-06912 : CMX: write error in datarq
  • ora-01878 : specified field not found in datetime or interval
  • ora-34000 : (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.
  • ora-15153 : cluster not in rolling upgrade
  • ora-19646 : cannot change size of datafile string from string to string
  • ora-40101 : Data Mining System Error string-string-string
  • ora-33005 : (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
  • ora-01229 : data file string is inconsistent with logs
  • ora-12667 : Shared server: outbound transport protocol different from inbound
  • ora-26094 : stream format error: input column overflow
  • ora-02025 : all tables in the SQL statement must be at the remote database
  • ora-24422 : error occurred while trying to destroy the Session Pool
  • ora-00566 : cannot request processor group - NUMA not enabled
  • ora-02372 : data for row: string
  • ora-06321 : IPA: Cannot reach the remote side
  • ora-19754 : error reading from change tracking file
  • ora-26519 : no memory available to allocate
  • ora-30451 : internal error
  • ora-12914 : Cannot migrate tablespace to dictionary managed type
  • ora-01272 : REUSE only allowed when a file name is provided.
  • ora-02086 : database (link) name is too long
  • ora-23363 : mismatch of mview base table "string" at master and mview site
  • 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.