OAC CSV download limit

OAC is external PaaS Cloud application from Oracle.  It does allows the customer to change some of the configuration parameters similar to on-premise OBIEE application.

But good thing is that OAC automated provisioning process itself take care of setting the correct configuration parameters based on the shape of the OAC Service instance.  There should not be a need for customer to change those parameters post provisioning.

For example,  CSV download parameter in the instanceconfig.xml are set based on the OAC shape.

Based on the Shape,

OC3M - CSV download limit is 65K

OC4M - CSV download limit is 500K

OC5M - CSV download limit is 1M

These values get set during provisioning and there should not be a need to change it further unless really needed.

OAC have two separate configuration settings for limiting excel and csv downloads,  DefaultRowsDisplayedInDownload and DefaultRowsDisplayedInDownloadCSV respectively.

BICS report execution result in "the user request exceeded the maximum query governing execution time"

Some of the reports in BICS results in following error but same report in on-premise OBIEE run successfully against the same Datawarehouse.

Odbc driver returned an error (SQLExecDirectW).
 Error Details
Error Codes: OPR4ONWY:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred.
Please have your System Administrator look at the log for more details on this error. (HY000)
State: HY000. Code: 43113. [nQSError: 43113] Message returned from OBIS.
Please have your System Administrator look at the log for more details on this error. (HY000)
State: HY000. Code: 43119. [nQSError: 43119] Query Failed:
Please have your System Administrator look at the log for more details on this error. (HY000)
State: HY000. Code: 60009. [nQSError: 60009] The user request exceeded the maximum query governing execution time.
Please have your System Administrator look at the log for more details on this error. (HY000)
Please have your System Administrator look at the log for more details on this error. 

This is due to the Query governor set in BICS.  Given that BICS is a cloud service and in cloud,  user query need to be controlled in order to make sure environment is stable and can scale.  This is done by introducing the query governors.  Query execution timeout is set to 600 seconds and this is hard limit.  Customer cannot request to change this hard limit for their BICS instance so report need to be re-design so that DB query runs within 600 seconds.

This limitation will not be there in OAC since OAC is external PaaS and customer will be able to change the limit as per their own requirement. 

DAC 11.1.1.6.4 intermittent Crash




It has been notice DAC 11.1.1.6.4 Server crash intermittently and it need to be restarted.  Crash is following.




# A fatal error has been detected by the Java Runtime Environment:


# # SIGSEGV (0xb) at pc=0x00007fcf752b21b0, pid=112882, tid=140528723429696
# # JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x6541b0] jni_GetLongArrayRegion+0xd0
# # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
# # An error report file with more information is saved as: # /oraclebi/DAC11G/dac/hs_err_pid112882.log
# # If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# ORA-24550: signal received: [si_signo=6] [si_errno=0] [si_code=-6] [si_int=0] [si_ptr=(nil)] [si_addr=0x4e220001b8f2] kpedbg_dmp_stack()+362

Reference:

 

ORA-24550 Signal Received Error From Client Based Application (Doc ID 1284564.1)

 

CAUSE

 

Diagnosability features which are turned on by default on Oracle 11g Release 2 causes the problem.

Parameters are:

DIAG_ADR_ENABLED

DIAG_SIGHANDLER_ENABLED

DIAG_DDE_ENABLED

 

SOLUTION

 

1. Such errors can occur if the "Diagnosability" features are 'ON'.

To turn off the OCI signal handler and re-enable standard Operating System failure processing, place the following parameter setting in sqlnet.ora:

DIAG_SIGHANDLER_ENABLED=FALSE

By default this parameter is set to true.

If you want to see the old behavior you can simply turn off the feature by placing the following parameter setting in your client side sqlnet.ora file under $ORACLE_HOME/network/admin directory.

2. In addition, please turn off other Diagnostics parameters as well by placing the following entries in the client side or server sqlnet.ora file. i.e., from where the application is run.

DIAG_ADR_ENABLED=OFF

DIAG_SIGHANDLER_ENABLED=FALSE

DIAG_DDE_ENABLED=FALSE

 

Note:

Changes to client side SQLNET.ORA requires only application restart.

Where as changes to SQLNET.ORA on Database side requires only restart of the listener.