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 : 28-07-2017

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

  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-38463 : invalid XML Tag list
  • ora-31405 : cannot make changes while change set string is advancing
  • ora-13065 : cannot delete a child layer with a parent layer
  • ora-06577 : output parameter not a bind variable
  • ora-03249 : Uniform size for auto segment space managed tablespace should have atleast string blocks
  • ora-30162 : The OCIFile context is not initialzed
  • ora-12489 : default label not within clearance range
  • ora-39091 : unable to determine logical standby and streams status
  • ora-09953 : scggc: unexpected return of a lock convert
  • ora-13775 : inconsistent datatype in input cursor
  • ora-12557 : TNS:protocol adapter not loadable
  • ora-16713 : the resource guard timed out while servicing the request
  • ora-04065 : not executed, altered or dropped string
  • ora-13425 : function not implemented
  • ora-31507 : %s parameter value longer than maximum length string
  • ora-13916 : Invalid value "string" specified for parameter "string"
  • ora-25108 : standby lock name space exceeds size limit of string characters
  • ora-06445 : ssvpstevrg: Incorrect parameters passed to function call
  • ora-39783 : Invalid direct path transaction active
  • ora-08450 : invalid specification of CR in picture mask
  • ora-26734 : different datafiles_directory_object parameter must be specified
  • ora-23496 : can not change disabled status for "string" and "string"
  • ora-14187 : partitioning method for LOCAL index is inconsistent with that of the underlying table
  • ora-36722 : (XSALLOC02) In AGGMAP workspace object, you specified an NA or ZERO sourceval but supplied formula workspace object as your source for ALLOCATE.
  • ora-16243 : paging out string bytes of memory to disk
  • ora-29321 : too many datafiles added since the point-in-time
  • ora-01868 : the leading precision of the interval is too small
  • ora-01522 : file 'string' to be renamed does not exist
  • ora-28331 : encrypted column size too long for its data type
  • 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.