Oracle AppsDBA R12.2 : Patching ADOP : Overview & Finding Patch 

Yes I'm also looking for same

mohammed Javeed these are part of our apps dBa training . If you want to learn apps dBa I suggest to look at free masterclass at k21academy.com/appsdba02

@@K21Academy but cost is too much....we can't afford..

Thanks @@ramur226 and glad for being open and honest. I understand where you are coming from as I was exactly same back in 2004-05 when I was transforming from being an Oracle Apps DBA to Oracle Identity Management. I was nervous about spending 2700 £ Oracle IDM training as I just moved to London at that time and my monthly salary was 2400 £. After 9 months of stressful learning on my own with 1000s of pages from 10s of Oracle Manuals, and losing number of 600-750 £ per day contract opportunities, I finally joined IDM course and there is no looking back... Since then I have invested a lot of money 💰 on learning latest on Cloud and always got much more back in higher Day Rate (salary) and better role. I no longer look Learning as expense but investment. Ask just one question to yourself, how much money you are losing by not investing in yourself or how much more you can earn (or not to worry about future and enjoy what you do) if you know what employers are looking for. We are very confident on our comprehensive step by step training program that if you perform all hands-on labs covered in program K21Academy.com/oci05 and watch theory videos (50+) not only you’ll clear certification but can get a better paying job on Cloud and earn lot more. Every person who attends live lessons and does hands-on lab says it’s totally worth. You can see all the testimonials at k21academy.com/testimonials I hope this helps to see the bigger picture, don’t hesitate to reach out to my team at contact@k21academy.com if you have any more questions. -Atul

The error "ORA-12514: TNS: listener does not currently know of service requested in connect descriptor" typically indicates that the listener service is not aware of the database service specified in the connect descriptor. This can occur due to incorrect configuration, network issues, or the service not being registered with the listener. To resolve this issue, you should verify the following: 1. Check the Listener Status : Ensure that the listener service is running and configured correctly. Start the listener service if it's not running 2. Verify the Listener Configuration : Check the listener configuration file (listener.ora) for any errors or misconfigurations. Ensure that the listener is configured to listen on the correct port and that the service names are correctly specified 3. Check the Service Registration: Verify that the database service is registered with the listener. Check the listener log files for any errors related to service registration. If the service is not registered, restart the listener or check the database configuration 4. Check the Connect Descriptor : Verify that the connect descriptor in your application or script is correctly formatted and specifies the correct service name. Ensure that the service name matches the one registered with the listener 5. Check Network Connectivity: Verify that there are no network connectivity issues between the client and the database server. Ensure that the client can connect to the database server using other methods, such as SQL*Plus 6. Check the TNSNAMES.ORA File : Verify that the tnsnames.ora file is correctly configured and contains the necessary entries for the database service. Ensure that the file is located in the correct directory and that the entries are correctly formatted 7. Check the SQLNET.ORA File : Verify that the sqlnet.ora file is correctly configured and specifies the correct resolution method for the connect identifier. Ensure that the file is located in the correct directory and that the entries are correctly formatted 8. Check the Database Configuration : Verify that the database is correctly configured and that the service name is correctly specified in the database configuration files By following these steps, you should be able to identify and resolve the issue causing the "ORA-12514" error.