|
|
|
Junior Member
 
Group: Forum Members
Last Login: 8/25/2008 5:46:43 PM
Posts: 23,
Visits: 73
|
|
I have moved 5G permspace under user A for his stored procedures. After he finished the task, he dropped his procedures and I tried to move out this 5G permspace back to other database. Move space succeeded, but I noticed that Teradata administrator still shows that there is about 40 bytes maxperm under this user.
has any body encounered that before?
Besides, we are using V2R5. At the time this user was running his procedures, one node of our teradata database down and then the whole system down. Our maitenance guys said 'There was a problem with node 1-5 accessing VPROCS due to a DR in the PDE portion of the database. The DR is fixed in the latest patches for 5.1.2.' Could anybody explain that too..
Thanks,
Ivy
|
|
|
|
|
Supreme Being
Group: Forum Members
Last Login: Today @ 6:49:01 AM
Posts: 180,
Visits: 578
|
|
Hello,
What is the CurrentPerm for that user?
MaxPerm is the maximum perm-space in bytes, ever occupied. It is not the current perm-space!
HTH.
Regards,
Adeel
|
|
|
|
|
Supreme Being
Group: Forum Members
Last Login: Today @ 5:02:02 PM
Posts: 225,
Visits: 531
|
|
Adeel seems to be confusing MaxPerm with PeakPerm.
You can change MaxPerm to anything you want using the MODIFY USER statement.
|
|
|
|
|
Supreme Being
Group: Forum Members
Last Login: Today @ 6:49:01 AM
Posts: 180,
Visits: 578
|
|
|
Exactly ... Jim Chapman is right ... my bad!! :(
|
|
|
|
|
Junior Member
Group: Forum Members
Last Login: 8/25/2008 5:46:43 PM
Posts: 23,
Visits: 73
|
|
Thank you guys. I used modify user to change the permanent space to 0 bytes
Ivy
|
|
|
|