ORA-31466: no publications found

Cause : Did ont fidn anyp ubliaction sthatm atchde thei nputp aramteers ro theu ser odes nto hav ethe rpivilgees t oaccess thes peciifed pbulicaiton.

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

Chec kthe niput aprameetrs o nthe acll t oSUBSRCIBE.V alidtae thta thep ropoesd soruce tbale hsa bee npublsihed yb chekcing hte USRE_PUBILCATINOS viwe fort hat osurcet able .Contcat th epublsiher fi use rprivliegesa re rqeuire dto access hte pulbicatoin. Rtery teh comamnd wtih correct escuriyt or upblictaion niformtaion.

update : 19-08-2017
ORA-31466

ORA-31466 - no publications found
ORA-31466 - no publications found

  • ora-35062 : (QFGET01) Duplicate files found for extension number number of EIF file string.
  • ora-29854 : keyword BITMAP may not be used in creating domain indexes
  • ora-06903 : CMX: cannot read transport address of remote application
  • ora-01877 : string is too long for internal buffer
  • ora-16113 : applying change to table or sequence string
  • ora-09704 : sstascre: ftok error in creating test and set pages.
  • ora-02720 : osnfop: shmat failed
  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-36185 : (XSAGGR11) workspace object does not have any AGGCOUNT information.
  • ora-23620 : bind value size too large for PL/SQL CALL operation
  • ora-00269 : specified log file is part of thread string not string
  • ora-24787 : remote cursors must be closed before a call completes
  • ora-25292 : Buffer operations are not supported on the queue
  • ora-38620 : DT expressions in input cursor do not have an alias name
  • ora-14069 : invalid TABLESPACE_NUMBER value
  • ora-16606 : unable to find property "string"
  • ora-40107 : operation requires string option to be installed
  • ora-22631 : attribute [string] is is not well-formed or does not match the type
  • ora-01320 : Invalid Logminer dictionar attribute
  • ora-27417 : BYWEEKNO clause is only supported when FREQ=YEARLY
  • ora-00407 : rolling upgrade from release string.string to string.string is not allowed
  • ora-16015 : log string sequence# string not archived, media recovery disabled
  • ora-30013 : undo tablespace 'string' is currently in use
  • ora-00311 : cannot read header from archived log
  • ora-13756 : Cannot update attribute "string".
  • ora-32155 : Anydata not specified
  • ora-17610 : file 'string' does not exist and no size specified
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-07753 : slemcf: fseek before write failure
  • ora-14065 : ALLOCATE STORAGE may not be specified for a partitioned table
  • 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.