I don't see that in the documentation - final classmethod CatchupDB(DBList As %String, JournalLocation As %String = "", ByRef DBErrList As %String) as %Integer
- Log in to post comments
I don't see that in the documentation - final classmethod CatchupDB(DBList As %String, JournalLocation As %String = "", ByRef DBErrList As %String) as %Integer
A low impact way to do this would be take a SAN snapshot of production and mount the snapshot in test.
Intersystems discusses this in External Backup.
The easy way to retain some database is mount them from a different set of disks/filesystem.
If you have a DR mirror but not a SAN you could just shutdown the DR mirror and do a cold backup.
If test is a separate mirror the whole test mirror will have to be refreshed due to mirror headers. If test is part of the same mirror as production then the data is already there.
I think you can q to exit that debug mode.
In two really key ways multi-volumes datasets don't allow you to escape limits you might want to escape.
The max size of a multi-volume dataset is the same as a single file - 34 TB (33553904 MB) for 8K database. Intersystems is working to increase the max size.
An integrity check also treats it as if it was a single file. This is only going to be more of an issue as the max size increses.
1.9Tb will be days assuming ssd storage and slower if not.
I would test a small amount during a low period.
Since you are on Cache still make sure it is ok to compact/truncate with your version.
Run an integrity check after to validate the DAT.
Expect large wij growth.
Do @Enrico Parisi's suggestion of a small amount first during a low utilization time.
Mirror and shadow targets have to be done separately.
As a guess the shell is interpreting $job rather than passing it to IRIS.
try this
echo 'set sc=$$CheckList^Integrity(,,,,5) do Display^Integrity() kill ^IRIS.TempIntegrityOutput(+$job)' | iris session [INSTANCE] -U %sys
one issue with this approach is you need to get the same IRIS session that the integrity check ran in.
An instance name is not guarantied to be unique.
hostname/ip + instance is.
For example the instance name of our failover primary and backup is the same they are just on different hosts.
We use DNS name not IP addresses though so we have DNS/instance for SystemName.
I would ask your vendor what they develop on so you don't have to listen to an excuse around a support issue.
I would check that your iris.key file exists and has not expired.
Not sure where messages.log is on Windows but I would look at that over a Windows log.
Guessing the upgrade did iris start [instance] nostu to not run any user code on startup.
iris help start
**** iris usage ****
Syntax:
iris start <instance name> [parameters]
Description:
Run the instance's irisstart procedure to bring InterSystems IRIS up.
Optional parameters:
quietly -> non-interactive, with minimal dialog
nostu -> don't run startup routine (^STU)
help -> list supported parameters
EmergencyId=username,password -> start up in emergency mode
Any other value is taken as a configuration file name with '.cpf' appended.
If a configuration file is not specified, the file 'iris.cpf' is used.
Example:
iris start mystuff quietly <- uses file 'mystuff.cpf'
Notes:
Some instances might not have support for a particular parameter,
or a new parameter could have been added. For a list of supported
parameters for a specific instance, type:
iris start <instance name> help
The only thing from the preinstall doc that looks like a service is a webserver.
You might look at this Estimating Memory Requirements.
Did you do this? Semaphore Deletion Setting
I would not completely replace users with LDAP.
Database owner and admin should be local to the system.
Make sure your LDAP source is not a single server.
The recommendation is XFS from Supported File Systems.
There are some clear warningssugestions in the documentation but very reasonable.
Customizing Start and Stop Behavior with ^%ZSTART and ^%ZSTOP Routines - Design Considerations
Using the ^ZMIRROR Routine
One issue to consider is on Failover or DR mirrors the code might need to be in ZMIRROR not ZSTART.
I don't think you need more than normal production code awareness.
I don't have the linux version running now but the docs say
systemctl status ISCAgent.service
or if you have ISCAgentCtrl
ISCAgentCtrl status
Usage: ./ISCAgentCtrl start|stop|restart|status|usage
The irisstat command with the -u option allows you to look at this without going into iris.
You can also look at locks in the portal - Monitoring Locks
This looks like what you want.
https://cedocs.intersystems.com/ens20171/csp/documatic/%25CSP.Documatic…
I would consider upgrading to the latest Cache before using compact and truncate.
Run an integrity check after to validate it didn't cause corruption.
Read this to see if applies
https://www.intersystems.com/product-alerts-advisories/alert-possible-d…
I had to debug an application LDAP issue and I used to Apache Directory Studio.
It turned out that the user had been copied from one OU to another and not moved.
Not sure that you have seen that Intersystems deprecated SAM November 13th.
Log level is not always a good indicator of how big a deal what is being logged is.
For example:
2 [Generic.Event] Unable to allocate shared memory minimum - this error prevents startup so critical
1 [Generic.Event] MirrorServer: Lost ReadDmn (ACK) connection to async - loss of connection connection to a mirror doesn't rate as even a warning?
Any maximum you set less than free space on the filesystem will just hit the limit sooner.
The instance could use more RAM in the global buffer and maybe more filesystem space.
You should look at this and this.
I would expect the WIJ to close to force it to the disk about every 80 seconds ie every write cycle.
my quick testing:
$while true; do
> ls -l IRIS.WIJ | cut -f 10-13 -d ' '
> sleep 40
> done
Oct 26 12:26 IRIS.WIJ
Oct 26 12:27 IRIS.WIJ
Oct 26 12:27 IRIS.WIJ
Oct 26 12:28 IRIS.WIJ
Oct 26 12:28 IRIS.WIJ
Oct 26 12:30 IRIS.WIJ
Oct 26 12:30 IRIS.WIJ
Oct 26 12:31 IRIS.WIJ
Oct 26 12:31 IRIS.WIJ
Oct 26 12:32 IRIS.WIJ
Oct 26 12:32 IRIS.WIJ
Oct 26 12:34 IRIS.WIJ
Oct 26 12:34 IRIS.WIJ
Oct 26 12:35 IRIS.WIJ
Oct 26 12:35 IRIS.WIJ
Oct 26 12:36 IRIS.WIJ
You should look at this - Write Image Journaling and Recovery
The WIJ can live in other places.
Cache 2018.1.8 is supported on Redhat 8
This should get you started - Installing Caché on UNIX®, Linux, and macOS