Other

Question: What are the effects of increasing the value of the pd_max_users operand in order to accommodate more users?

Answer: For details about the effects of increasing the value of the pd_max_users operand, see 9.5 Handling an increase in the number of users.

(2) No UAP is connected, but user identification information is displayed

Question: No UAP is connected, so why is user identification information displayed when the pdls -d act command is executed?

Answer: If transaction rollback was not completed after a server process was aborted or rerun, the user identification information is retained. This user identification information will be deleted once transaction rollback is completed.

(3) Can the system time be changed?

Question: I want to change the system time to do some tests. Is it possible to change the system time?; What would be the effects of forcibly advancing or rolling back the system date or time?

Answer

Although you can advance the system date or time, it is not recommended that you do so.

HiRDB stores date and time information in the system log files, status files, and dictionaries for use during HiRDB restart, etc. Date and time information is also stored in the work files of various utilities for use in several types of checking.

Advancing the date and time: There is no serious problem in advancing the time, but statistical information may not be displayed correctly, or for some period the time may not be updated in messages. If the date and time are changed during HiRDB startup processing, the results cannot be guaranteed. There may also be OS consequences.

Rolling back the date and time: The results cannot be guaranteed because various problems may result, such as restart errors, database recovery errors, invalid system waits, etc. For these reasons, forcibly rolling back the date or time is not advisable. If the date and time are rolled back for testing purposes, the system and databases will have to be rebuilt from the beginning.

(4) Authorization identifiers and passwords are not being recognized correctly

Question: Why are authorization identifiers and passwords not being recognized correctly?

Answer

It is possible that upper- and lower-case letters are not being recognized correctly. If lower-case letters are included, the character strings must be enclosed in quotation marks ("). Otherwise, the lower-case letters will be regarded as upper-case letters.

Example

SELECT * FROM "user05".TABLE05;

Appendix A.11 Other

(1) Increasing the number of executing users

(2) No UAP is connected, but user identification information is displayed

(3) Can the system time be changed?

(4) Authorization identifiers and passwords are not being recognized correctly