TM1 Forum

Hi, I accidentally zeroout }ClientGroups cube data through a TI
I have two users both with Admin access, apparently both wiped, hence unable to log back in to restore all user groups manually.

Q.
1. Is there a way to recover/roll back the cube data?
2. Does zeroing out }ClientGroups cube (all leaf nodes of }Client and }Group added to zerooutview) wipes all clients from each group?
3. If there are no }Clients added Admin group, how can I add one? I don't have admin access now

Thanks!

1. Yes, assuming you have a backup simply restore the .cub file
2. This depends on the security mode. If you use CAM security with Cognos or AD groups, once the users log back in that cube will be re-populated automatically. If you use native TM1 groups then yes, they are wiped out from the groups

Whatamouth wrote:3. If there are no }Clients added Admin group, how can I add one? I don't have admin access now

First recover the said cube from your backup, then we will have a look at it again, if needed.

mvaspal wrote:1. Yes, assuming you have a backup simply restore the .cub file
2. This depends on the security mode. If you use CAM security with Cognos or AD groups, once the users log back in that cube will be re-populated automatically. If you use native TM1 groups then yes, they are wiped out from the groups

Thank you!
So, I'm working on restoring the cube. I checked the current .cub file, check sum is just the same as backup as I'm unable to perform savedata at the moment (or can I do it without admin?)
I think there are pending updates to other cubes too. If I kill the service, will I lose all these data changes from all the cubes?
Sorry for the add-on questions.

Br

If you have not saved data yet then copy the .cub off the disc.
Unload the cube in perspectives (not sure if this is available vs ctrl cubes, normally on the right click menu) or stop the instance.
Copy the .cub back into the data directory.
Restart the instance / load the cube

Assuming you have filesystem access:

1. Create a .rux file to map one user to admin.
2. Restart server.
3. Log in to account which now has admin access.
4. Add admin access to second user.
5. Log out first user. Log in via second user, delete rulefile, grant access to first user (and whomever else).

If you shutdown the service from the Services snap in, it will do a SaveDataAll automatically. If you TaskKill and have transaction logging enabled, it will replay uncommitted transactions automatically on restart.

This will get you back in ASAP, but obviously not restore old data. If you have access to the old cube fiel, that's the best way to restore access. If there's a delay to restore the old data, you can get back in this way and restore old data later.

Matt

Thanks heaps fellas! Got the cube and users access back
I've confirmed, stopping the service automatically performs SaveDataAll prior to actually stopping the server instance.

Br