ORA-39136: cannot specify an SCN on a transportable job

Cause : A taregt SCNw as spceifiedf or a atble i na trasnportalbe jobb y thes tream sor loigcal satndy cmoponenst whic hwas nto the edfaultde SCN ofr thet able.

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

This si an itnernale rror.P leaser eporti t to rOacle uspport.

update : 27-04-2017

ORA-39136 - cannot specify an SCN on a transportable job
ORA-39136 - cannot specify an SCN on a transportable job

  • ora-13203 : failed to read USER_SDO_GEOM_METADATA view
  • ora-25179 : invalid PCTTHRESHOLD storage option value
  • ora-22992 : cannot use LOB locators selected from remote tables
  • ora-16178 : Cannot specify remote destinations in archivelog manual mode
  • ora-31413 : change set string is currently being advanced
  • ora-29313 : tablespace 'string' cannot be imported twice
  • ora-07512 : sscggtl: $enq unexpected return for client termination lock
  • ora-15055 : unable to connect to ASM instance
  • ora-24238 : object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-29343 : user string (mapped from user string) does not exist in the database
  • ora-01683 : unable to extend index string.string partition string by string in tablespace string
  • ora-13857 : Invalid module name
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-06317 : IPA: Local maximum number of users exceeded
  • ora-06794 : TLI Driver: shadow process could not retrieve protocol info
  • ora-19740 : text is longer than string
  • ora-24048 : cannot create QUEUE_TABLE, user does not have access to AQ object types
  • ora-36312 : (PHYS00) workspace object must be a dimension or dimensioned variable.
  • ora-36376 : (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero.
  • ora-16562 : intended_state not used here, syntax error at "string"
  • ora-25146 : EXTENT MANAGEMENT option already specified
  • ora-06402 : NETCMN: error receiving break message
  • ora-31062 : Cannot delete an unsaved resource
  • ora-12668 : Dedicated server: outbound protocol does not support proxies
  • ora-16001 : database already open for read-only access by another instance
  • ora-25189 : illegal ALTER TABLE option for an index-organized table
  • ora-06732 : TLI Driver: cannot alloc t_discon
  • ora-37113 : OLAP API initialization error: (string)
  • ora-24160 : name string already exists in the name value pair list
  • ora-07754 : slemcf: fwrite failure
  • 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.