Using the 3.2.4 CLI against a 126.96.36.199 PAM clustered node, when running the CLI command
capam_command cmdName=searchTargetAccount > AllTargetAccounts.xml
The XML content returned only contains 10K rows (10K accounts) but we know there are many more accounts in the system; 33K more, to be exact.
I found this command, thought i might give it a try:
capam_command cmdName=setReportRowLimit rowLimit=50000
but, it doesn't seem to increase the result set size limit, but it ran successfully.
Is there a known issue or limitation with the number of rows returned by a CLI search command?
thanks in advance.
Hi Seb, Please review the documentation page for this command at https://docops.ca.com/ca-privileged-access-manager/3-2-4/en/programming/credential-manager-remote-cli-and-java-api/credential-manager-cli-commands/searchtargetaccount
It includes a description of parameters Page.Size and Page.Number.
well now I feel a bit embarrassed.
I thought I had combed through that page.
sorry I missed it.
Although, i did get an error:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at org.a.a.a.b(Unknown Source)
at org.a.a.a.a(Unknown Source)
at org.a.a.a.c(Unknown Source)
at org.a.a.a.next(Unknown Source)
Ok, good. I believe the limit was not the memory of the VM, but the Java max heap memory setting of the tomcat process running in the VM, which uses setting -Xmx1536M in current PAM releases.