While working on one of the production issue I came across one error in oracle.
ORA-06508: PL/SQL: could not find program unit being called
When i checked in the database i can't found any invalid objects using below query.
select * from user_objects where status <> 'VALID';
Once all the packages are recompiled by me and then tried there was no error. This is occurring in Database from sometime. Did anyone faced any such issues in past.
Can you please help me finding the RCA for this issue.
Related
I have a large database that I am currently exporting from Microsoft Access (Version 2006 Build 13001.20384) to PostgreSQL 10.12 (Ubuntu 10.12-0ubuntu0.18.04.1). So far this worked very well, but I have problems with one particular table. When I start the export, I get the following error message:
ERROR: syntax error at or near '/';
Error while executing the query (#1)
Unfortunately I do not know how to deal with this error message and I have not found any information about this message on the Internet. Maybe someone here can help me.
[I copy my previous comment, since it contains useful content for the solution, so this question can appear as solved... and it contains also suggestions for someone in the future with the same problem.]
You say "with one particular table"... maybe the name of that table or a column name of that table is a keyword for postgresql and not for access (it seems the name contain a '/').
Try to split the import if you don't know the table to isolate the problem. E.g. divide the query in 2 halves, then do the same for the half that give the syntax error. If you update your question with the table definition that gives error we can help you find the exact problem if you can't figure it out.
While I compile and debug every procedure I'm getting error SEVERE: NULL Preferences during startup And oracle SQL developer getting hung.
I faced this issue yesterday. As I was looking for an answer, I came across this unanswered question of yours - !
However by going through how some queries of the stored procedure were written, I realized that:
There was another way of writing it with the same result set.
I was missing single quotation for a query assigned to a variable.
Thus, making those corrections, I found the problem gone - !
keep the backup by renaming the system_cache folder at below path:
C:\Users\{username}\AppData\Roaming\SQL Developer\system17.4.0.355.2349
The error will be gone.
I am getting an error in talend. PFA.
Please find more details of the mapping.
Can you please help me here?.
Thank You
Tom
This was an issue with code generation of Talend Bigdata version.
There were 5 subjobs in my job.
I was testing the functionality of last three subjobs.(Off late i have added 3 extra tSql components into my 4th subjob , which you can see in the screenshot).
For that i have de-activated the first two subjobs.(I have de-activated the first two subjobs earlier as well and unit tested which was fine)
I assumed this was the issue with code generation of talend.
(Earlier also I faced similar issue with .map() function of tSql component. That time i deleted tSql component and created it again and issue went away.)
I proceeded with the following trial and error method.
I closed the job and reopened again ( issue exists)
I restarted Talend tool and reopened again (issue exists)
I deleted the tSql components and created them again (issue exists)
I activated the de-activated subjobs and then checked again(ISSUE DISAPPEARED)
I'm running jobs through Datastage with the DELETE then INSERT connector. I'm having several jobs failing for this error:
DB2_Connector: DB2 reported: SQLSTATE = 02000 Native Error Code = 100, Msg = IBM[CLIDriver][DB2/NT64] SQL01000W No row was found for FETCH, UPDATE, or DELETE
When I run the delete statement in Data Studio directly in DB2, it gives this same error so I know it's a DB2 error, not a Datastage error.
Is there anyway to supress the message in Datastage or when I run the statement in DB2 is there anyway I can keep that message from coming up? It's stopping my DS jobs now with a Fatal error and not continuing to load.
There has got to be a way to turn off the message. I know in SQL Server if no rows are found it does not give this error, it just says zero or doesn't return records but in DB2 this error is coming up and I'm not sure if there is a way to turn it off.
First of all, you seem to be confused about precisely what an error is, and what a message is.
An error is when something goes wrong.
A message is when some piece of software is kind enough to let you know that something went wrong.
From this it follows that suppressing a message has no bearing whatsoever on the actual error. Your software is not failing because of the message, your software is failing because something is going wrong. Receiving a message about it is actually a good thing: the alternative would be your software failing without you being given any clue whatsoever as to what is going wrong.
Suppressing or otherwise ignoring errors is like hiding your head in the sand: you are still going to end up as meal.
So, what you need to make go away is the error, not the message.
Which means that you have to figure out what you did wrong.
Luckily, you have the message giving you a hint as to what you did wrong, though you have to keep in mind that messages are sometimes misleading.
SQLState 02000 is not an error, it is a warning. (And note that DB2_Connector is not saying ERROR!!!1!:, it is saying DB2 reported:.) Luckily JDBC issues warnings when it detects situations that might be indicative of errors; there is a lot of software out there that ignores JDBC warnings, (essentially hiding your head in the sand for you, how nice,) but luckily DB2_Connector reports them.
What this means is that one of two things is going wrong:
Either your assumption that it is okay if no rows are found is wrong, and the fact that no rows were found is the cause of your problem, which means that you have to somehow make sure that some rows are found, or
Your assumption that it is okay if no rows are found is correct, in which case the warning reported has absolutely nothing to do with the problem at hand, so it can safely be ignored, and you have to look at the problem elsewhere.
I designed a report in iReport that has a straight forward query as the main report and a sub report with another simple query. Neither query has any parameters passed to it, however they both deal with timestamps extensively.
The combined report runs fine within iReport and if i remove the sub-query and load both into JasperReports Server they will run independently. However, when I try to run the full report that includes the sub-report, I get the following error and stack trace:
The server has encountered an error. Please excuse the inconvenience.
Error Message
net.sf.jasperreports.engine.JRRuntimeException: Parameter "DATABASE_TIMEZONE" does not exist.
Error Trace
net.sf.jasperreports.engine.JRRuntimeException: Parameter "DATABASE_TIMEZONE" does not exist.
at net.sf.jasperreports.engine.query.JRAbstractQueryExecuter.getValueParameter(JRAbstractQueryExecuter.java:606)
at net.sf.jasperreports.engine.query.JRAbstractQueryExecuter.getValueParameter(JRAbstractQueryExecuter.java:621)
at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.getValueParameter(JRTimezoneJdbcQueryExecuter.java:150)
at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.<init>(JRTimezoneJdbcQueryExecuter.java:134)
at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuterFactory.createQueryExecuter(JRTimezoneJdbcQueryExecuterFactory.java:50)
at net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(JRFillDataset.java:728)
at net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(JRFillDataset.java:629)
at net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(JRBaseFiller.java:1159)
at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:802)
at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:746)
at net.sf.jasperreports.engine.fill.JRFillSubreport.fillSubreport(JRFillSubreport.java:640)
at net.sf.jasperreports.engine.fill.JRSubreportRunnable.run(JRSubreportRunnable.java:59)
at net.sf.jasperreports.engine.fill.JRThreadSubreportRunner.run(JRThreadSubreportRunner.java:205)
at java.lang.Thread.run(Thread.java:619)
This is is a known bug as far as I can tell, but isn't receiving much attention. Has anyone encountered this error and come up with a workaround or at least an explanation of what is going on?
Just so that this question has an answer:
My solution was to modify my SQL query to return all my data in one query and remove the sub-report. This seems like a silly work around for a fairly important feature but it is working in the meantime.