Hi,
What are all the thins to check in IFS application after a DB refresh.
How can I identify that it is perfectly refreshed?
Please help...
Thanks in advance.
Thanks and regards,
Hari
Solved
Things to check in IFS application after DB refresh
+9Best answer by Ragaventhan Sathananda
Hi
It depend on your environment settings and configurations you use. But in general terms I would recommend below points to check before and after the refresh whether it has the same parameters.
- batch queue configuration
- delivery differences (installed Components window)
- system parameters, plsqlap environment tab & IFS Connect Configurations
- License Management window information
- Connect server’s listener port (Setup IFS Connect window)
- database backup method configuration and archive logs parameters
- undo tablespace names
- oracle directory names and paths
These are the basic which came to my mind to be verified after the database refresh and this is what we follow as a standard as well. But there's a catch if you are using customized tables and information on the environment those need to be verified as well.
Hope this clears your question! If this comment satisfies you please mark it as the best answer so others will also get benefited from this post.
This topic has been closed for comments
+15Hi
It depend on your environment settings and configurations you use. But in general terms I would recommend below points to check before and after the refresh whether it has the same parameters.
- batch queue configuration
- delivery differences (installed Components window)
- system parameters, plsqlap environment tab & IFS Connect Configurations
- License Management window information
- Connect server’s listener port (Setup IFS Connect window)
- database backup method configuration and archive logs parameters
- undo tablespace names
- oracle directory names and paths
These are the basic which came to my mind to be verified after the database refresh and this is what we follow as a standard as well. But there's a catch if you are using customized tables and information on the environment those need to be verified as well.
Hope this clears your question! If this comment satisfies you please mark it as the best answer so others will also get benefited from this post.
Ragaventhan S - https://www.linkedin.com/in/ragaventhan-sathananda/
+9Ragaventhan Sathananda wrote:
Hi
It depend on your environment settings and configurations you use. But in general terms I would recommend below points to check before and after the refresh whether it has the same parameters.
- batch queue configuration
- delivery differences (installed Components window)
- system parameters, plsqlap environment tab & IFS Connect Configurations
- License Management window information
- Connect server’s listener port (Setup IFS Connect window)
- database backup method configuration and archive logs parameters
- undo tablespace names
- oracle directory names and paths
These are the basic which came to my mind to be verified after the database refresh and this is what we follow as a standard as well. But there's a catch if you are using customized tables and information on the environment those need to be verified as well.
Hope this clears your question! If this comment satisfies you please mark it as the best answer so others will also get benefited from this post.
Hi Ragav,
Thanks a lot.
Regards,
Hari
1 person likes this
+19Write a script, and don’t rely on a manual process. Avoiding the embarrassment when your nonproduction system sends an email to a customer or a supplier will make such an effort worth your time.
Our postdbcopy.sql script is now over 1200 lines long. There’s just too much to remember to do.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.