| HOWTO:FDM Import Error Using SQL Integration Script "The RPC Server is Unavailable" | |||||
|
|
|||||
| Modified 19-APR-2010 Type HOWTO | |||||
Hyperion Financial Data Quality Management - Version: 11.1.1.0.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.
When attempting to import data into FDM from teradata using a SQL integration script the import fails. After running for a 10+ mins the import process fails with the error message:
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
When running an import of the same recordset using a flat file, the import completes successfully.
The memory utilized by uspAppsv.exe on the FDM server was ~ 1750MB before it crashed and returned the error.
It is possible to use a SQL integration script to import a large record set of data?
What is occuring during the import process using the SQL Integration Script is that the SQL Query is being ran and the upsappsrv.exe process is reaching the maximum memory limit of 2GB for a .NET process on a windows 32 bit operating system and is crashing, returning the RPC is unavailable error message.
When FDM processes an import via flat file it utilizes Oracle or SQL Server database processes that do not require use of the same methods as a SQL Integration script.
A SQL integration script is an inefficient method to load large amounts of data. Based on what is being seen, the record set that is being retrieved is large and is causing the app server process to reach the 2 GB memory limit and crash due to memory limit constraints with Microsoft .NET.
The recommendation is to proceed forward using a flat file exported from teradata to load the source data into the FDM application. This will allow for the large record set to be imported into the application successfully and will not exceed the 2GB Limit for .NET with the usappsrv.exe process on the FDM application server.
It might be possible to write the script to process the file in smaller chunks. This is entirely custom and would be outside of support.
Information in this document applies to any platform.
Goal
When attempting to import data into FDM from teradata using a SQL integration script the import fails. After running for a 10+ mins the import process fails with the error message:
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
When running an import of the same recordset using a flat file, the import completes successfully.
The memory utilized by uspAppsv.exe on the FDM server was ~ 1750MB before it crashed and returned the error.
It is possible to use a SQL integration script to import a large record set of data?
Solution
What is occuring during the import process using the SQL Integration Script is that the SQL Query is being ran and the upsappsrv.exe process is reaching the maximum memory limit of 2GB for a .NET process on a windows 32 bit operating system and is crashing, returning the RPC is unavailable error message.
When FDM processes an import via flat file it utilizes Oracle or SQL Server database processes that do not require use of the same methods as a SQL Integration script.
A SQL integration script is an inefficient method to load large amounts of data. Based on what is being seen, the record set that is being retrieved is large and is causing the app server process to reach the 2 GB memory limit and crash due to memory limit constraints with Microsoft .NET.
The recommendation is to proceed forward using a flat file exported from teradata to load the source data into the FDM application. This will allow for the large record set to be imported into the application successfully and will not exceed the 2GB Limit for .NET with the usappsrv.exe process on the FDM application server.
It might be possible to write the script to process the file in smaller chunks. This is entirely custom and would be outside of support.
GKontos
Comments