on 12-12-2013 3:04 PM
I think there was an issue at some point with the transaction logging table not getting cleaned out. There is a some info about it in sap note 1537813:
RunTransactionExpirationCheck - off by default. When MII is started, if RunTransactionExpirationCheck is on, MII will check the XMII_TRANSACTIONS table for high expiring transactions. Transactions that are found with high expiring values will be corrected as will the expiration value for any transactions that call that transaction. This helps solve the problem where the expiration value is 21600000.
A BLS service mode is provided to update all transactions which may have a high expiration value. To run the service you will need to use the URL:
http(s)://: /XMII/Illuminator?Service=BLSManager&Mode=FixHighExpiringTransactions
Where http(s) is the correct protocol (http or https) is the fully qualified server name, and is the correct port number. This service will take some time to run and should only be run once.
Link below:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
6 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.