Then either the RRDB or the programming of the G4 is wrong. Not meant as an insult, it's easy to transpose digits, everyone's done it.
Two thoughts:
You could create a P25 system on the G4 with the sys ID programmed, but give a search range for the control channels. That would cover the situation where the RRDB has the right sys ID, but the incorrect CC freq. Set the timeout for CC search to be a lot higher before it times out. (Edited to add: checked the RRDB against the FCC database and they agree on the CC frequencies. Make sure you enter all of them in.)
On the other hand, perhaps the RRDB has the sys ID wrong but the right CC frequencies - create a P25 system with all of the CCs but with the sys ID (and site IDs) wildcarded.
While you could both wildcard the sys ID and give a search range for the CCs, I suspect the G4 might just latch onto ARMER and stay there - but it could latch onto the LAX system too. Possibly worth a try.
Make sure you enable diagnostics in the display so you can note the CC, Sys ID and Site ID when you do latch onto the system.