SQL Developer BUG - ORA-00980 Synonym Translation No Longer Valid

We have a read only database of our Production and when I try to access any data using the SQL Developer, I'm getting the following Error.
Error at Command Line:1 Column:14
Error report:
SQL Error: ORA-00980: synonym translation is no longer valid
If I access the same from SQL Plus, Toad or SQL Station, It works fine. Seems some error in SQL Developer.
Any one with Ideas or suggestions.

we have DB cloned from Prod everynight and is available for us on readonly access. No read /write privs to any user including DBA.
I think the DB is opened with ALTER DATABASE OPEN READ ONLY;
Also to mention, all the tables in the db can be accessible only by read only user who was given select permission on synonyms.
--VB

Similar Messages

ORA-00980: synonym translation is no longer valid

Hi
I get the following error when try to insert xml
SQL> ed
Wrote file afiedt.buf
1 insert into "bulkCmConfigDataFile_TAB"
2 values(
3 XDB_UTILITIES.getXMLFromFile('Test.xml','DATA_DIR').
4 createSchemaBasedXML('http://127.0.0.1:8081/public/xsds/configData.xsd')
5* )
SQL> /
XDB_UTILITIES.getXMLFromFile('Test.xml','DATA_DIR').
ERROR at line 3:
ORA-00980: synonym translation is no longer valid
I ran the following sql
SQL> select STATUS from dba_objects where object_name = 'XDB_UTILITIES';
STATUS
VALID
The directory was created using
SQL> show user
USER is "XMLUSER"
SQL> create or replace directory data_dir as 'c:\xml';
Directory created.
What could be the problem here?
Thanks
Devashish
10g Rel2

Devashish
Unfortunately the way your XML Schema are designed I do not think XML DB is going to be able to handle them. The problem is the substituion group for vsData. Basically it defines a very flat structure which will require a table with more than 1000 columns to persist. Since the structure is very flat we cannot use the technique of pushing sections of the structure into out-of-line tables to store it, which is the normal workaround.
This looks to me like a case of the classic mistake of modeling a Java Object structure directly into XML. In general this makes no sense. There is no common information between all of the different elements of the substition group or the vsData type, so there is no point in having all the members of the substition grouip descend from a single abstract type. You could just as easily model your XML Structure as a choice of any of the elements defined in the substition group. If new elements need to be introduced this could be done using extension of the existing complexType with new choices.
The advantage of this approach is that you can push each of the possible chocies into a seperate table, and avoid the 1000 column limit..
Sorry for the bad news, hope you have flexibility to re-architect the XML Schema. Note that this should not affect the instance documents

Form - Remote DB - Link - Synonym - ORA-00980: synonym translation invalid

All,
I have created a PUBLIC LINK AND SYNONYM on a table in a remote DB using the Navigator/Wizard. I then tried to create a FORM using the Wizard. In the Wizard I press enter to FINISH and I receive the error listed below.
Note I have read and read and re-read all info available to me on the subject. Some posts on MetaLink and these forums suggested that the Link and Synonym made Public - they are as they live in the Public Schema. Another doc stated the "Returning" statement was the problem.
I have tested this in SQLPLus and it works fine.
What is the is problem with this and how do I fix it?????
Thanks,
Bill G...
Error creating package PORTAL_DEMO.FORM_1
Line/Column Error
242/18 PL/SQL: ORA-00980: synonym translation is no longer valid
236/65530 PL/SQL: SQL Statement ignored
284/65 PL/SQL: ORA-00980: synonym translation is no longer valid
284/28 PL/SQL: SQL Statement ignored
284/16 PLS-00341: declaration of cursor '_tc' is incomplete or malformed
290/25 PL/SQL: Item ignored
321/30 PLS-00320: the declaration of the type of this expression is incomplete or malformed
321/13 PL/SQL: SQL Statement ignored
357/38 PLS-00320: the declaration of the type of this expression is incomplete or malformed
354/13 PL/SQL: Statement ignored
369/34 PLS-00320: the declaration of the type of this expression is incomplete or malformed
369/17 PL/SQL: SQL Statement ignored
380/30 PLS-00320: the declaration of the type of this expression is incomplete or malformed
380/13 PL/SQL: SQL Statement ignored
387/38 PLS-00320: the declaration of the type of this expression is incomplete or malformed
384/13 PL/SQL: Statement ignored
400/26 PLS-00320: the declaration of the type of this expression is incomplete or malformed
400/9 PL/SQL: SQL Statement ignored
464/63 PL/SQL: ORA-00980: synonym translation is no longer valid
464/26 PL/SQL: SQL Statement ignored

Yeah, it is pretty simple really. Metalink note 174618.1 covers it. The note is for Rel1, but the same works with Rel2.
Cut and paste doesnt work well here, but if you cant access the note, I can reformat it and paste it in here.

Error ORA-00980: synonym translation is no longer valid when i issue

i accidentally drop one of my table. To bring it back i used Imp tool. But it gives an error ORA-00980: synonym translation is no longer valid when i issue
Select * from ship_sched_fact_notice_det
Action taken using Imp
Username: erpdada
Password:
Connected to: Oracle Database 10g Release 10.1.0.2.0 - Production
Import file: EXPDAT.DMP > e:\erpdada_august13.dmp
Enter insert buffer size (minimum is 8192) 30720> 30720
Export file created by EXPORT:V10.01.00 via conventional path
Warning: the objects were exported by SYSTEM, not by you
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
List contents of import file only (yes/no): no > y
Import entire export file (yes/no): no > n
Username: erpdada
Enter table(T) or partition(T:P) names. Null list means all tables for user
Enter table(T) or partition(T:P) name or . if done: ship_sched_fact_notice_det
Enter table(T) or partition(T:P) name or . if done: .
"CREATE PUBLIC SYNONYM "XMLTYPE" FOR "SYS"."XMLTYPE""
"CREATE TABLE "SHIP_SCHED_FACT_NOTICE_DET" ("SSFND_ITEM_NOT_DET_ID" NUMBER, "
""SSFN_FACTORY_ID" VARCHAR2(40) NOT NULL ENABLE, "SSFN_FAC_NOTICE_ID" NUMBER"
" NOT NULL ENABLE, "SSD_SHIP_ITEM_ID" NUMBER NOT NULL ENABLE, "OI_ITEM_ID" N"
"UMBER NOT NULL ENABLE, "ORDER_TYPE" VARCHAR2(1), "SSFND_ITEM_CODE" VARCHAR2"
"(300), "SSFND_QTY" NUMBER, "SSFND_CTN" NUMBER, "SSFND_TOT_CBM" NUMBER, "SSF"
"ND_REM1" VARCHAR2(256), "SSFND_REM2" VARCHAR2(256), "SSFND_UNIT_ID" VARCHAR"
"2(40), "SSFND_IS_EXCL_SUMMARY" VARCHAR2(1)) PCTFREE 10 PCTUSED 40 INITRANS"
" 1 MAXTRANS 255 STORAGE(INITIAL 81920 FREELISTS 1 FREELIST GROUPS 1 BUFFER_"
"POOL DEFAULT) TABLESPACE "ORDER_DATA01" LOGGING NOCOMPRESS"
. . skipping table "SHIP_SCHED_FACT_NOTICE_DET"
"GRANT DELETE ON "SHIP_SCHED_FACT_NOTICE_DET" TO "SHIPMENT_NOTICE""
"GRANT INSERT ON "SHIP_SCHED_FACT_NOTICE_DET" TO "SHIPMENT_NOTICE""
"GRANT SELECT ON "SHIP_SCHED_FACT_NOTICE_DET" TO "SHIPMENT_NOTICE""
"GRANT UPDATE ON "SHIP_SCHED_FACT_NOTICE_DET" TO "SHIPMENT_NOTICE""
"CREATE UNIQUE INDEX "PK_SHIP_SCHED_FACT_NOTICE_DET" ON "SHIP_SCHED_FACT_NOT"
"ICE_DET" ("SSFND_ITEM_NOT_DET_ID" ) PCTFREE 10 INITRANS 2 MAXTRANS 255 STO"
"RAGE(INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLE"
"SPACE "ORDER_DATA01" LOGGING"
"ALTER TABLE "SHIP_SCHED_FACT_NOTICE_DET" ADD CONSTRAINT "PK_SHIP_SCHED_FAC"
"T_NOTICE_DET" PRIMARY KEY ("SSFND_ITEM_NOT_DET_ID") USING INDEX PCTFREE 10 "
"INITRANS 2 MAXTRANS 255 STORAGE(INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1"
" BUFFER_POOL DEFAULT) TABLESPACE "ORDER_DATA01" LOGGING ENABLE "
"ALTER TABLE "SHIP_SCHED_FACT_NOTICE_DET" ADD CONSTRAINT "SHIP_SCHED_FACT_NO"
"TICE_DE_FK1" FOREIGN KEY ("SSD_SHIP_ITEM_ID") REFERENCES "SHIPPING_SCHEDULE"
"_DETAILS" ("SSD_SHIP_ITEM_ID") ENABLE NOVALIDATE"
"ALTER TABLE "SHIP_SCHED_FACT_NOTICE_DET" ADD CONSTRAINT "SHIP_SCHED_FACT_NO"
"TICE_DE_FK2" FOREIGN KEY ("SSFN_FAC_NOTICE_ID") REFERENCES "SHIP_SCHED_FACT"
"ORY_NOTICE" ("SSFN_FAC_NOTICE_ID") ENABLE NOVALIDATE"
"ALTER TABLE "SHIP_SCHED_FACT_NOTICE_DET" ENABLE CONSTRAINT "SHIP_SCHED_FACT"
"_NOTICE_DE_FK1""
"ALTER TABLE "SHIP_SCHED_FACT_NOTICE_DET" ENABLE CONSTRAINT "SHIP_SCHED_FACT"
"_NOTICE_DE_FK2""
Import terminated successfully with warnings.
I drop the old synonym and re-create it but still it gives the same error...

Since you are on 10g did you try flashback table feature - http://tonguc.wordpress.com/2007/01/01/oracle-10g-flashback-versions-query-drop-table-and-recyclebin-management/
FLASHBACK TABLE <tabname> TO BEFORE DROP;
If you didnt use purge option, the dropped object is on your recyclebin - http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9018.htm#sthref9593
Best regards.

ORA-00980 Synonym Translation Error caused by WebUtil?

I have setup WebUtil and applied some CLIENT_TEXT_IO code to a form. Everything worked perfectly running through 9iDS so I configured 9iAS to do the same.
When running the form through 9iAS I am getting the ORA-00980 error about synonym translation. The same database instance was used so so webutil_db shouldn't be the problem but I cannot see how this error could be related to WebUtil - anyone have any ideas.
The CLIENT_TEXT_IO code still works even though this error is reported.

Since you are on 10g did you try flashback table feature - http://tonguc.wordpress.com/2007/01/01/oracle-10g-flashback-versions-query-drop-table-and-recyclebin-management/
FLASHBACK TABLE <tabname> TO BEFORE DROP;
If you didnt use purge option, the dropped object is on your recyclebin - http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9018.htm#sthref9593
Best regards.

PL/SQL:ORA-00980: synonym translation is no longer valid

Hi,
I have imported the full database (9i) and import terminated succefully.But
I got the followinf errors:
ORA-04098: trigger 'UNITE.CAPT_FEE' is invalid and failed re-validation .
There are number of triggers where we got the same error.
Please help
Thanks
Harinder

Hi ,
There are problems in the views as well as in triggers.
the db links are same but tnsname.ora was different.
so i have made an entry in tnsnames.ora file.
Used parameter files:
/raid1/app/oracle/product/9.2/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
)SERVICE_NAME = ocklive.world)ST = ock)(PORT = 1529))
OK (10 msec)
But when i have executed this sql query
select * from tab@ocklive
i have recieved the following error :
ORA-12154: TNS:could not resolve service name
but this is working fine on another system from where i have imported data.
Thanks
Harinder

Has anyone else seen ORA-00980 synonym errors when using XMLConcat?

Hi,
Using 10.2.0.2 ( as shown by select * from v$instance), I get an ORA-00980 "Synonym translation is no longer valid" message.
This occurs for any attempt to use XMLConcat, for a simple example:
SELECT XMLConcat(XMLElement("first", 'Steve'),
XMLElement("last", 'Jones'))
AS "RESULT"
FROM dual;
I'm guessing that there is/was a problem with an upgrade since I've found a few vague references to a bug fixed in 9.2 that seems to point in that direction.
Our DBA team is looking into it, but it would be interesting to hear if other developers hit the same problem and if there was a relatively easy fix.
Thanks!

SQL> conn / as sysdba
SQL> @catnoqm
SQL> @catqmTry to fix it first though manually. The upgrade probably went wrong somehow...
On the FAQ on this forum Mark states:
XML DB FAQ
How do I uninstall XML DB ? How do I re-install XML DB ?
Posted: Sep 11, 2006 10:28 PM mdrake in response to: mdrake
To uninstall XML DB run the sql script $ORACLE_HOME/rdbms/admin/catnoqm.
Note that running this script will
1. DELETE ALL INFORMATION STORED IN THE ORACLE XML DB REPOSITORY AND XDB DATABASE SCHEMA
2. PERMANENTLY INVALIDATE ANY XMLTYPE TABLES OR COLUMNS THAT ARE ASSOCIATED WITH A REGISTERED XML SCHEMA.
IF THE XDB USER IS DROPPED THERE IS NO WAY TO RECOVER THE DATA IN THESE XMLTYPE TABLES OR COLUMNS.
Please do not uninstall XML DB in a production database without explicit instructions from Oracle Support to do so.
To re-install XDB, after running catnoqm.sql, stop and restart the instance and then run catqm as described in the previous post. Backup your database first via RMAN...
Edited by: Marco Gralike on Feb 13, 2009 8:11 PM

Another SQL Developer bug - End of file in comment

I found another SQL Developer bug in version 3.0.0.4.
If I try to compile some package from file (so I open file with package body in SQL Developer and assign it to some connection) with this kind of comment: /* comment */ behind end of package, I get this error
I got Error(1250,28): PLS-00111: end-of-file in commentFunny is, that when the package is compiled directly from the database - it works.
When I try to compile the package from file with this kind of comment --comment behind the end of package, it also works...

Hi, I think I finally got it. This looks like an ugly fat bug :)
First, we are not using the .sql extensions. For package specification - we use .pks. For package body - we use .pkb.
Create this script:
CREATE OR REPLACE PACKAGE TEST_xxx AS
PROCEDURE TEST_PROCEDURE;
END TEST_xxx; /*0123456789*/Now save this as e.g. "TEST.pks" file. Open this file in SQL Developer and compile it. You will get the "Error(3,27): PLS-00111: end-of-file in comment".
Now look at the result in the database -> Open the package specification from the database and you see this:
create or replace
PACKAGE TEST_xxx AS
PROCEDURE TEST_PROCEDURE;
END TEST_xxx; /*0123456789*The last slash is missing...
Now go back to the file with the package specification and delete one letter from the comment. Compile it again... it works now.
It looks like the length of this kind of comment is limited to 9 characters.
The limitation is there only when:
1) Compiling from file with different extension than .sql !!! If you rename the file to "TEST.sql", SQL Developer opens it as a script file and runs it as a script, so there is no problem with it.
2) It has to be this kind of comment: /* */. One line comments are not limited.

SQL Developer bug or database bug?

This is in SQLPlus,
SQL> alter session set nls_date_format='YYYY-MM-DD HH24:MI:SS';
Session altered.
SQL> select sysdate from dual;
SYSDATE
2006-10-12 12:31:20
SQL> begin
2 dbms_session.set_nls('nls_date_format','''DD-MON-YY''');
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> select sysdate from dual;
SYSDATE
12-OCT-06
dbms_session.set_nls works perfectly, however, in SQLDeveloper, when I run the same thing:
alter session set succeeded.
SYSDATE
2006-10-12 12:30:42
1 rows selected
anonymous block completed
SYSDATE
2006-10-12 12:30:42 <-- Notice how the format is not changed.
1 rows selected
I am wondering if this is a SQLDeveloper bug(more likely) or database bug?

I run the following in SQLDeveloper,
alter session set nls_date_format='YYYY-MM-DD HH24:MI:SS';
select * from v$nls_parameters where parameter='NLS_DATE_FORMAT';
select sysdate from dual;
begin
dbms_session.set_nls('nls_date_format','''DD-MON-YY''');
end;
select * from v$nls_parameters where parameter='NLS_DATE_FORMAT';
select sysdate from dual;
Here's the output from SQL Developer:
alter session set succeeded.
PARAMETER VALUE
NLS_DATE_FORMAT YYYY-MM-DD HH24:MI:SS
1 rows selected
SYSDATE
2006-10-13 12:38:06
1 rows selected
anonymous block completed
PARAMETER VALUE
NLS_DATE_FORMAT DD-MON-YY <-- This proves it's not the database.
1 rows selected
SYSDATE
2006-10-13 12:38:06
1 rows selected
I believe this proves beyond doubt, that it's SQL Developer bug. Perhaps caching NLS settings?

Hi, i am new to oracle, SQL DEVELOPER:- ERROR:- ORA-01918

Hi,
I am new to oracle, and i have installed Oracle database 12c enterprise edition, and oracle jdeveloper 12c for adf web application development,
I created a database and a new connection in it using sql developer, however while trying to create new user with the name db1 by right clicking on other users. by following the instructions in oracle documentation site. i get the error that new user db1 doesnt exist, and gives error:- ORA-01981. i even tried by changing the username as i thought may be it doesnt support alphanumeric name, but still i get the same error.
So please tell me how to create a new user. is there any way to get out of this ora:-01918, as i googled and it says this is a bug.
My os is win 7 x64(amd processor ).
Thank you
Baldwin

A new user (called a schema in Oracle) is created using the CREATE USER SQL command. You need to be signed in as the SYS schema/user or as a schema that has been granted the rights to create schemas.
12c database comes in two basic flavours. Container database (containing pluggable databases). Standard database. If connected to a container database, you cannot create standard user schemas - you need to be connected to a pluggable database.
Also, your question has no relevance to either the SQL or PL/SQL languages - the subject matter of this forum. Please repost your question to a more appropriate forum dealing with SQL-Developer issues.

SQL Developer Bug: NVL() function error when debug/run stored procedure

Version:
SQL Developer: 1.5.3 (build main-5783)
Oracle DB connected: Oracle9i Enterprise Edition Release 9.2.0.6.0
Stored procedure code like this:
procedure search(V_STATUS_IN IN CHAR(1)) is
begin
declare
V_STATUS CHAR(1) := NULL;
begin
V_STATUS := NVL(V_STATUS_IN, '%'); -- error line
end;
end;
The stored procedure runs well (I mean no oracle exception) when called through Java code (and in TOAD). But when debug/run in SQL Developer, following error at the error line:
$Oracle.EXCEPTION_ORA_6502:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
--------------------------------------------------*/

What parameter are you passing in? It is possible you are trying to cram a multibyte character into a singlebyte container. What are the nls settings for the database and for sqldeveloper?

Fallo en SQL Developer , bugs in SQL Developer

He detectado que si hacemos clic con el botón derecho sobre una tabla y seleccionamos EXPORT ==> SQL INSERT. la exportación no se lleva a cabo.
¿Alguien ha detectado este problema?

Mucho mas tarde, doy confirmacion del problema en mi sistema Linux SuSE 10.0 con Oracle 10g release 2 y la ultima version de SQL Developer (Build 14.67). No tengo ningun dato en el fichero ni en el "clipboard". Pero si no selecciono todas las columnas, el fichero o el clipboard se rellenan normalement. Eso explica que algunos dicen que funciona y otros que no funciona.
Como solucion pratica, creo una vista (view) con una columno mas ( *, 1 as nada) y no la selecciono. Solo me queda cambiar el nombre de la tabula en el texto SQL que produce la exportacion.
A few weeks later, I certify there is a bug (en my Linux SuSE 10.0 system con Oracle 10 g release 2 and Build 14.67 of SQL Developer). I obtain an empty file or nothing in the clipboard. If I don't select all fields, the file or clipboard are full of data. This explains why some assert there is no problem and other say there is one. As a practical solution, I created a view with an extra field ( *, 1 as dummy) and didn't select it. I only have to rename the table in the exported SQL text.

Stupid SQL Developer bug

Hi,
I have this problem. I open some table in SQL Developer, scroll in the middle, put focus on some cell or entire line. Then I open another table in another tab. Then switch back to the first tab. The focus is still as it was before, however the table is always scrolled to the first line.
This happens everytime when I switch to another table tab, so I need always to scroll back. When I switch e.g. on another package and then back, the scroll position is correct...
Is there any workaround or bug fix. It is really annoyng...
Thanks, Dan

Well the carret position is preserved even when you scroll down with a mouse and than click some cell or select entire line. Only the table is scrolled back to the top...
Lets hope they will fix this soon together with dozen of other bugs.
To mwickham:
I use pin by default, otherwise new table would open always in the same window...

Sql developer bug list

I find the link of sql developer 1.2 bug fix list. Where can I find the place of bug list of sql developer 1.2 so that we can pay attention to the bugs?

With a Metalink account, users can ask if a bug has been logged and if it is logged to be made public. If there is no bug, a new bug can be logged. Development teams across Oracle use the bug database all the time to track issues. This includes issues between releases and those raised during the development cycle. It does not make sense to publish all bugs.
While monitoring this forum, the SQL Developer team logs bugs and, when related to a specific thread, provide the bug number and publish the bug. Metalink remains the primary support mechanism for logging and tracking bugs.
Sue

SQL Developer bug? It does not return DATEs if database is only MOUNTED

I'm logging into a mounted database as SYS to check on things using the V$ views, but any query I do involving DATEs never returns any data. If I remove the DATE column, the query works fine. If the database is OPEN, the query works fine with the DATEs. This is a bit of a problem when I want to check on standby databases for example. Is this the way it's supposed to work?
Help!

The original thread appeared to have gone nowhere, so I raised the issue again. If I have violated forum rules, please forgive me.
I have a choice of using either TOAD or SQL Developer at the site that I have just started at, and I have not used either much. I was leaning towards SQL Developer as its price to functionality ratio is very attractive. However, this issue of not working with a mounted database is a show stopper for me for SQL Developer as I prefer to use a single tool that handles all of the DBA work that I do. So far, TOAD does, and SQL Developer does not.

SQL Developer BUG - ORA-00980 Synonym Translation No Longer Valid

Similar Messages

Maybe you are looking for