中文版 | 
HOME   |   ABOUT US   |   NEWS TREND   |   PRODUCT SYSTEM   |   CLIENT RESOURCES   |   TROUBLESHOOTING   |   CONTACT US
 
 
 
 
  HOME >> Troubleshooting
 

1、Why can not the financial analysis chart of the credit system be displayed?
Cause:Lack of appropriate office plug-in.
Solution:Download and install a plug-in in Office Help
2、Why is the excel data exported from credit system very slow?
Cause:There are few displayed bars per page in the configuration.
Solution:there are a number of displayed bars per page when configure the query. Increasing the number of displayed bars per page can accelerate to export the excel.
3、Having modified the institutional relationship on the management system, why is it still not effective?
Cause:The agency relational table reads the relational table into memory for use every time you start the tomcat service.
Solution:In each maintenance, after saving and generating institutional relations, restart the tomcat service.
4、End-day error reporting at the backstage of the data warehouse: SQL0964C The transaction log for the database is full.
Cause:The transaction log is full, resulting in operation being not continued.
Solution:Can modify the size of three parameters: DB2 LOGFILSIZ, LOGPRIMARY, LOGSECOND to increase the log space. Use the following command to change the log file size:
       db2 update db cfg for database name using
       logfilsiz 50000 logprimary 20 logsecond 10
       DB20000I UPDATE DATABASE CONFIGURATION The command is completed successfully.
       For these configuration parameters, the changes cannot take effect until all applications disconnect with the database.
5、Log management system prompts the wrong user password.
Cause:(1) The user forgets the password.
               (2) Front and back-server network is interrupted.
               (3) Restart the backstage database.
Solution:(1) Forgetting password, look for the system administrator to reset the initial password, and then modify.
               (2) On network interruption and database resetting, you need to restart the front tomcat server.
6、The operator checks transaction to increase teller serial number, without evidence.
Cause:Whether the backstage configuration transaction runs water error.
Solution:The zxr field Corresponded by ggjydyb should be replaced by 0
7、The operator cannot deal, or the background prompts communication failure.
Cause:Temporary file error generated by the foreground and background is due to lack of space in foreground and background.
Solution:Regular cleaning of foreground and background tmp, files in txt.
8、The intermediate platform replaces the So dynamic database file, why is it sometimes useful and sometimes unuseful?
Cause:In order to facilitate the procedures maintaining, the intermediate platform do many treatments with dynamic call mode and dynamic database. When the program master is in handling, first you need to determine whether the dynamic library is opened, if it is opened and not closed, it will not be re-opened, therefore the replacement so may not be called, and generally the long procedure will all be like this.
Solution:You can restart the service.
9、When the intermediate platform database operates procedures, why is manual implementation ok? While crontab regular execution is not successful?
Cause:when use the database, you need to configure some environment variables, such as the informix database needs to configure INFORMIXDIR, INFORMIXSERVER etc. parameters, generally set in Profile or. Kshrc in the ksh environment. After users log in, the environment variables in the current shell enter into force, but when regular implemented in the crontab background, due to in the shell program execution environment, which is different from the environment we logged on the user, does not automatically set these parameters, you need to call function putenv ()in the program to set their own.
 
Copyright © 2010 NewChoiLink All Rights Reserved.  Add: 8th Jinlian Building, No. 35 Zhuhe Street, Zhongshan District, Dalian