Usually the most informative error messages regarding a failed ETL run can be found in the BDS Console.
Navigate to BDS Console via http://<BDSSAHostname>:9080/bds
Where BDSSAHostname -> Hostname or IP Address of the BDSSA Server.
9080 -> Default port number which Metadata Navigator uses in BSARA/BDSSA
Navigate to BDS Console via https://<BDSSAHostname>:9443/bds
Where BDSSAHostname -> Hostname or IP Address of the BDSSA Server.
9443\443 -> Default port number which Metadata Navigator uses in BSARA/BDSSA
Then Enter credentials -
Username: BDSAdmin
Password: <password specified at installation time>
When you initially login to BDS Console then go to ETL Management-->ETL Status- >ETL Run. From here you will see the top level ETL sessions listed such as the following:
0_BSARA_ETL
1_MASTER
2_FOUNDATION
FOUNDATION_DIMENSION
FOUNDATION_BRIDGE
..
3_COMPLIANCE
3_JOB_ACTIVITY
..
4_INVENTORY
...
etc
Each of these sessions will have a column on the left for the status.
Successful sessions will have a green checkmark icon, failed sessions will have a red stop sign icon and currently running sessions or sessions which were running when a stop_etl command was issued, will have a lightning bolt icon.
If the ETL job failed, at least one of these sessions will have a red stop sign icon.
The 0_BSARA_ETL session is the top level session so, if any of the other sessions have failed, 0_BSARA_ETL will also be marked as failed. Typically, the error messages contained in a failed 0_BSARA_ETL session can be ignored as they usually merely signify that another session has failed. So, for example, if the 4_INVENTORY session failed then both the 0_BSARA_ETL and the 4_INVENTORY session would be marked as failed but the most useful error messages will be found by drilling into the 4_INVENTORY session and not 0_BSARA_ETL.
Once the failed session has been determined, the next step is to drill into this session by clicking on the red stop sign icon. From here, a generic error message such as the following is often displayed:
java.lang.Exception: The scenario did not end properly.
at com.sunopsis.dwg.dbobj.SnpScen.a(SnpScen.java)
or
Message: 20200 : 72000 : java.sql.SQLException: ORA-20200: ETL failed for Site - 1
ORA-06512: at line 1
or
Message: 20101 : 72000 : java.sql.SQLException: ORA-20101: Scenario failed for Site - 1
ORA-06512: at line 1
or
50000 : S0001 : com.microsoft.sqlserver.jdbc.SQLServerException: Scenario failed for Site - 1.0
com.microsoft.sqlserver.jdbc.SQLServerException: Scenario failed for Site - 1.0
The above error messages merely signify that this session has failed but, in order to get to the real reason behind the failure, you will need to scroll down to the bottom of this page and look at the individual steps which comprise this ETL scenario.
Again, the steps will be marked as successful, failed or running. Drill into the failed step and a more useful exception should then be visible.
For some steps, there will be more sub-steps so you will need to drill further to find the root caused of the error.
Once you find the real error message, the root cause will often be obvious e.g. ORA-1652: unable to extend temp segment by 1024 in tablespace.
If the root cause of this error message is not obvious to either the BDSSA Admin or DBA, please submit a ticket to BMC Support and include the following details:
1) BDSSA Version - contents of <reports>/Version file
2) BSA Version - export of appserver details from BSA - Configuration -> Infrastructure Management -> Export Detail Report
3) Screenshot of top level of ETL management-->ETL Status homepage.
4) Error messages captured from ETL Status by following the steps in this article.
5) Was ETL previously working in this env? If so, when was the last successful run and did that correspond to any env change such as upgrade or DB move.
Related Products:
- BMC BladeLogic Decision Support for Server Automation (5 Report Viewers, 1 Query Studio)