'NOT A VARIABLE' is show

[Jeff LSY]

Hi,,,,, I have a problem...

I have 1 packages (and I've added debug information in my packages) and also PLSQL_DEBUG = TRUE

When call a procedure within a package body and then placing cursor to variables, instead of value shown, 'NOT A VARIABLE' is shown...

I have other old database... i have tested it... it's working... (different script, not same)

any idea?

Thanks

 

[Maxmix]

This happens then and now. Could you 'Add debug information' over again?

 

[Jeff LSY]

Hi! I have tried twice but still same.

Any idea?

 

[Maxmix]

Sorry, no ideas remain

 

[Hilarion]

Try using "Add debug info" in object tree on package specification and also on package body. Helped me sometimes.

 

[archer]

i have the same issue on occasion. i think it is related to the size of the package. i also recall someone saying that this could happen if the are 'too many' variables, though can't say how many is too many. Could also be related to database structure sizes, e.g., even though you are instructing oracle to add debug info, there isn't enough room for all the debug info. break points are also not working, right? but you can step into the code, right?

 

[Jeff LSY]

i have the same issue on occasion. i think it is related to the size of the package. i also recall someone saying that this could happen if the are 'too many' variables, though can't say how many is too many. Could also be related to database structure sizes, e.g., even though you are instructing oracle to add debug info, there isn't enough room for all the debug info. break points are also not working, right? but you can step into the code, right?

FYI, My old database's package is larger (1.14MB... all procedures & functions in one package body..) and able to show value when call a procedure within a package body... no problem.. But in new database... The existing new package is same as old package (1.14MB) except some additional code only... so not able to show value (NOT A VARIABLE) when call a procedure within a package body..... Two databases which both have the same level...the version is same...

 

[Jeff LSY]

Try using "Add debug info" in object tree on package specification and also on package body. Helped me sometimes.

I have tried twice but still same.... :-(

 

[Hilarion]

I have no idea if what archer suggested is right or not, but if it is, than still what you wrote may not rule out this cause.
Maybe physical (or virtual) server configurations differ between those Oracle Database systems and/or some Oracle DB configuration parameters differ (like SGA and/or PGA sizes).

What you could test, to make sure if the cause is on the DB side or on PL/SQL Developer side, is to use some another tool (like free "Oracle SQL Developer" from Oracle) to debug that code and check if the problem still occurs.

 

[Jeff LSY]

I have no idea if what archer suggested is right or not, but if it is, than still what you wrote may not rule out this cause.
Maybe physical (or virtual) server configurations differ between those Oracle Database systems and/or some Oracle DB configuration parameters differ (like SGA and/or PGA sizes).

What you could test, to make sure if the cause is on the DB side or on PL/SQL Developer side, is to use some another tool (like free "Oracle SQL Developer" from Oracle) to debug that code and check if the problem still occurs.

Oh Maybe.. Ok noted, i try figure out why.... Thank you to archer and Hilarion...