OrgAudit Extraction Keep on Processing

[Former Member]

Hi Experts,

I faced problem while start extraction on OrgAudit 4.0 SP1

It keep on processing. Please refer the log error below.

1. 07 May 2013 13:52:45 ERROR com.nakisa.Logger  -  : org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop Table OrgUnitHierarchytemp]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

2.

3. 07 May 2013 13:52:45 ERROR com.nakisa.Logger  - org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop Table OrgUnitHierarchytemp]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

4.

5. Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

6.

7.      at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)

8.      at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)

9.      at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)

10.      at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)

11.      at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)

12.      at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)

13.      at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)

14.      at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1033)

15.      at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)

16.      at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1909)

17.      at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1871)

18.      at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318)

19.      at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)

20.      at org.springframework.jdbc.core.JdbcTemplate$1ExecuteStatementCallback.doInStatement(JdbcTemplate.java:368)

21.      at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:342)

22.      at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:375)

23.      at com.nakisa.framework.data.commandProcessor.base.SqlAllPurposeCommandProcessor.executeCommand(SqlAllPurposeCommandProcessor.java:608)

24.      at com.nakisa.framework.data.commandProcessor.CommandProcessor.executeCommand(CommandProcessor.java:578)

25.      at com.nakisa.framework.data.commandProcessor.CommandProcessor.exec(CommandProcessor.java:526)

[StephenMillard · Accepted solution]

Lalit.

Looking at your log entries, the SQL being executed is:

Drop Table OrgUnitHierarchytemp

If that table does not exist (which is quite normal), Oracle will raise this as an error.  However usually the table is dropped so that it can be recreated so if it doesn't yet exist, then this should not cause an issue.

So do you have any other errors in your log - particularly towards where the job is stalling?

You may also want to review the last SQL being executed in your job (presumably actually the join stage if the above SQL is anything to go by) and then examine the table it refers to during the run.

If for example it is populating a table with data and you can see rows of data being added, but then it inexplicably stops; it may be that this can help you track down some "bad" data it might be failing on.

Hope that helps.

Regards,

Stephen.

[Former Member · Accepted solution]

Hi Stephen,

Thank you for your answer.  I just found that data extraction keep on processing is because I use IE Browser so I try to perform data extraction again via Chrome and it works.

[lukemarson · Accepted solution]

Hi Lalit,

That is peculiar. What version of IE are you using?

Best regards,

Luke

[Former Member · Accepted solution]

Hi Luke,

I have try both of IE version 10 and 9 but the result of these 2 version is the same. It keep on processing long time so I decided to use Chrome and it can work promply. I have no idea what happened on this.

[lukemarson · Accepted solution]

Hi Lalit,

IE10 is not supported, so you can ignore that. If the extract does not work in IE9 but does work in Chrome that does suggest that there is a problem with using IE. However, Chrome is also not supported by Nakisa!

When you run the extract in Chrome do you get the same errors as in IE?

Best regards,

Luke

[StephenMillard · Accepted solution]

Lalit.

It does seem curious that the job would run in Chrome but not in MSIE.  As Luke says, MSIE9 is supported, but Chrome is not.

1. Are you sure that the job ran successfully and to completion from Chrome and did not simply handle whatever MSIE was hanging on differently?  i.e. Did MSIE hang (and I'm not saying this is desired behaviour) on an issue and Chrome simply ignored it?
2. Did you look to see where the job was stalling in the cds.log when running from MSIE?
3. Have you made any changes to the extraction process or is this occurring for an out of the box (minimal changes) implementation?

Regards,

Stephen.

[Former Member · Accepted solution]

Hi Luke and Stephen,

1. Are you sure that the job ran successfully and to completion from Chrome and did not simply handle whatever MSIE was hanging on differently?  i.e. Did MSIE hang (and I'm not saying this is desired behaviour) on an issue and Chrome simply ignored it?

- Please refer my extraction process status and some of errors from my log when I do it via Chrome

I just recreate and perform it again today.

4289. 10 May 2013 17:24:49 ERROR com.nakisa.Logger - : org.springframework.jdbc.UncategorizedSQLException: StatementCallback; uncategorized SQLException for SQL [DROP INDEX OUH2_PARENTNO_IDX]; SQL state [72000]; error code [1418]; ORA-01418: specified index does not exist

4290. ; nested exception is java.sql.SQLException: ORA-01418: specified index does not exist

4291.

4292. 10 May 2013 17:24:49 ERROR com.nakisa.Logger - org.springframework.jdbc.UncategorizedSQLException: StatementCallback; uncategorized SQLException for SQL [DROP INDEX OUH2_PARENTNO_IDX]; SQL state [72000]; error code [1418]; ORA-01418: specified index does not exist

4293. ; nested exception is java.sql.SQLException: ORA-01418: specified index does not exist

4294.

4295. Caused by: java.sql.SQLException: ORA-01418: specified index does not exist

4296.

4297. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)

4298. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)

4299. at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)

4300. at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)

4451. 10 May 2013 17:24:49 ERROR com.nakisa.Logger - : org.springframework.jdbc.UncategorizedSQLException: StatementCallback; uncategorized SQLException for SQL [DROP INDEX ElementID_IDX]; SQL state [72000]; error code [1418]; ORA-01418: specified index does not exist

4452. ; nested exception is java.sql.SQLException: ORA-01418: specified index does not exist

4453.

4454. 10 May 2013 17:24:49 ERROR com.nakisa.Logger - org.springframework.jdbc.UncategorizedSQLException: StatementCallback; uncategorized SQLException for SQL [DROP INDEX ElementID_IDX]; SQL state [72000]; error code [1418]; ORA-01418: specified index does not exist

4455. ; nested exception is java.sql.SQLException: ORA-01418: specified index does not exist

4456.

4457. Caused by: java.sql.SQLException: ORA-01418: specified index does not exist

4458.

4459. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)

4460. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)

4461. at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)

4462. at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)

4938. 10 May 2013 17:24:50 INFO com.nakisa.Logger - SAP Extractor : Processing OrgHierarchyTablesAddDottedPositionAndOrgUnits - PositionHierarchy (Generating Tables for Orgnizational Hierarchy..)....

4939. 10 May 2013 17:24:50 ERROR com.nakisa.Logger - : org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop table PosDottedOrgUnitsTemp]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

4940.

4941. 10 May 2013 17:24:50 ERROR com.nakisa.Logger - org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop table PosDottedOrgUnitsTemp]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

4942.

4943. Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

4944.

4945. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)

4946. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)

4947. at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)

4948. at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)

5018. 10 May 2013 17:24:50 ERROR com.nakisa.Logger - : org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop table PosNotDottedTemp]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

5019.

5020. 10 May 2013 17:24:50 ERROR com.nakisa.Logger - org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop table PosNotDottedTemp]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

5021.

5022. Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

5023.

5024. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)

5025. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)

5176. 10 May 2013 17:24:50 ERROR com.nakisa.Logger - : org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop table PosDottedPositionsTemp2]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

5177.

5178. 10 May 2013 17:24:50 ERROR com.nakisa.Logger - org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop table PosDottedPositionsTemp2]; nested exception is java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

5179.

5180. Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

5181.

5182. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)

5183. at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)

5184. at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)

5185. at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)

5186. at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)

5187. at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)

5188. at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)

5189. at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1033)

2. Did you look to see where the job was stalling in the cds.log when running from MSIE?

- After it keep on processing very long time (more that 4 hrs) when I perform extraction via MSIE. I just close window, check the result at http://[servername]/OrgAudit/default.jsp and found that there have no any data.

3. Have you made any changes to the extraction process or is this occurring for an out of the box (minimal changes) implementation?

- No I have not change anything

[lukemarson · Accepted solution]

Hi Lalit,

There definitely seems like a problem with IE. I recommend opening an OSS message and providing details of your tests to show the problem.

Best regards,

Luke

[StephenMillard · Accepted solution]

Lalit.

The status output to the admin console is not always the most verbose or technically accurate.  Sometimes errors occur but are not reported as such back to the AdminConsole - in many cases for valid reasons (e.g. failure to drop a table that does not exist), in others ... well not so much.

The cds.log is the canoncial source when checking for activity and errors.  For most activities in the data population process, information will be logged to the cds.log.  Therefore if you run the job via AdminConsole in MSIE to the point at which it appears to hang and at that point check the cds.log you may be able to ascertain at exactly what point the job is halting - maybe even why.  You could then at least compare this against your log from a Chrome hosted run to see what step it should have completed.

Hopefully this will help you resolve your issue, or at least provide key information for any OSS you might raise.

Regards,

Stephen.