这样的话,就不能查看到物理的SQL 脚本执行的情况,判断数据是否有效性。
在RPD的管理会话中(menu manager -- session),可以看到用户的变量LOGLEVEL还是为0,应该是用户的初始变量被覆盖了,所以看不到LOG,修改变量的值为2就可以了。
日志级别共有5等级,看以参考BI ADMIN help文件,一般设置为2就可以了。
Logging Levels | Logging Level Information That Is Logged |
Level 0 | No logging |
Level 1 | Logs the SQL statement issued from the client application |
Logs elapsed times for query compilation, query execution, query cache processing, and back-end database processing | |
Logs the query status (success, failure, termination, or timeout). Logs the user ID, session ID, and request ID for each query | |
Level 2 | Logs everything logged in Level 1 |
Additionally, for each query, logs the repository name, business model name, presentation catalog (called Subject Area in Answers) name, SQLfor the queries issued against physical databases, queries issued against the cache, number of rows returned from each query against a physical database and from queries issued against the cache, and the number of rows returned to the client application | |
Level 3 | Logs everything logged in Level 2 |
Additionally, adds a log entry for the logical query plan, when a query that was supposed to seed the cache was not inserted into the cache, when existing cache entries are purged to make room for the current query, and when the attempt to update the exact match hit detector fails | |
Level 4 | Logs everything logged in Level 3 |
Additionally, logs the query execution plan. | |
Level 5 | Logs everything logged in Level 4 |
Additionally, logs intermediate row counts at various points in the execution plan. |
0 评论:
发表评论