maandag, mei 08, 2006

Invalid data type in view columns - 10gR2

Some views that were completely valid and usable in 10gR1 - and compiled without errors in 10gR2 did cause some peculiar errors in packages that depended on them. Even a normal select * from the_view failed.


ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-201: identifier 'UNDEFINED' must be declared

After a quick review I found that the - generated - view definition was different than I normally do:

create view x (a,b,c) as select a,b,c,d,e,f from y;

I am not sure about a bug (10.2.0.2) but it certainly is different behaviour than it used to be. A little tweek of the code made the view usable again:

create view x (a,b,c) as select a,b,c from y;

woensdag, mei 03, 2006

dbconsole: unable to connect to the database

Today it happened again. A 10gR2 database with a dbconsole installed on it was giving problems. The dbconsole was able to get the status of the instance and the agent was able to have the agent connected. It was not able to get the status of the listener. On this specific site there was a problem with system administration, to be more precise with the dns. Some settings were based on ip-address, some on qualified names. This eventually caused the problem. The fix in this case was to enter the full qualified name in the listener.ora and restart the dbconsole. After this all was running ok. Allways make sure that the addresses in listener.ora and targets.xml are the same.