[{"content":"Este es el primer post de mi nuevo blog. He decidido abandonar plataformas cerradas y montar mi propio \u0026ldquo;Data Center\u0026rdquo; estático usando Hugo, GitHub y Vercel.\n¿Por qué este cambio? Como DBA y SRE, tener control absoluto de mi infraestructura es innegociable. Con este setup consigo:\nRendimiento extremo (cero llamadas a BBDD). Soberanía de datos (mis posts son archivos Markdown en mi local). Flujo CI/CD (escribo, hago push y se despliega solo). Nos vemos en el próximo post.\n","permalink":"https://josecarlospavon.es/posts/hello-world/","summary":"\u003cp\u003eEste es el primer post de mi nuevo blog. He decidido abandonar plataformas cerradas y montar mi propio \u0026ldquo;Data Center\u0026rdquo; estático usando Hugo, GitHub y Vercel.\u003c/p\u003e\n\u003ch3 id=\"por-qué-este-cambio\"\u003e¿Por qué este cambio?\u003c/h3\u003e\n\u003cp\u003eComo DBA y SRE, tener control absoluto de mi infraestructura es innegociable. Con este setup consigo:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003e\u003cstrong\u003eRendimiento extremo\u003c/strong\u003e (cero llamadas a BBDD).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSoberanía de datos\u003c/strong\u003e (mis posts son archivos Markdown en mi local).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlujo CI/CD\u003c/strong\u003e (escribo, hago push y se despliega solo).\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003eNos vemos en el próximo post.\u003c/p\u003e","title":"Hello World: Migrando mi infraestructura a Hugo"},{"content":"RMAN-05541: no archived logs found in target database. Problem: You are getting RMAN-05541 error when duplicating database from a consistent (cold) RMAN backup.\nRMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 04/16/2021 12:57:12 RMAN-05501: aborting duplication of target database RMAN-05541: no archived logs found in target database Solution: The error should be resolved by using NOREDO clause for your duplicate command.\nDUPLICATE DATABASE TO \u0026#39;TEST02\u0026#39; BACKUP LOCATION \u0026#39;/mnt/export/oracle/orabackup/full/\u0026#39; NOREDO; RMAN-05501: aborting duplication of target database (Auxiliary file name /\u0026hellip;/\u0026hellip;/oracle/\u0026hellip;/oradata/perfstat01.dbf conflicts with a file used by the target database). Problem: You are getting RMAN-05001 error when duplicating database from a consistent (cold) RMAN backup.\nRMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 04/16/2021 13:12:33 RMAN-05501: aborting duplication of target database RMAN-05001: auxiliary file name /mnt/export/oracle/oradata/perfstat01.dbf conflicts with a file used by the target database Solution: The error should be resolved by using NOFILENAMECHECK clause for your duplicate command.\nDUPLICATE DATABASE TO \u0026#39;TEST02\u0026#39; BACKUP LOCATION \u0026#39;/mnt/export/oracle/orabackup/full/\u0026#39; NOFILENAMECHECK; 💡 Tip: Both can be used in the same DUPLICATE command in case we are duplicating non-OMF database from a cold RMAN backup as follows:\nDUPLICATE DATABASE TO \u0026#39;TEST02\u0026#39; BACKUP LOCATION \u0026#39;/mnt/export/oracle/orabackup/full/\u0026#39; NOREDO NOFILENAMECHECK; ","permalink":"https://josecarlospavon.es/posts/rman-duplicate-errors-05541/","summary":"\u003ch3 id=\"rman-05541-no-archived-logs-found-in-target-database\"\u003eRMAN-05541: no archived logs found in target database.\u003c/h3\u003e\n\u003cp\u003e\u003cstrong\u003eProblem:\u003c/strong\u003e\nYou are getting RMAN-05541 error when duplicating database from a consistent (cold) RMAN backup.\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-text\" data-lang=\"text\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRMAN-00571: ===========================================================\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRMAN-00571: ===========================================================\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRMAN-03002: failure of Duplicate Db command at 04/16/2021 12:57:12\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRMAN-05501: aborting duplication of target database\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRMAN-05541: no archived logs found in target database\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003e\u003cstrong\u003eSolution:\u003c/strong\u003e\nThe error should be resolved by using NOREDO clause for your duplicate command.\u003c/p\u003e","title":"RMAN-05541 \u0026 RMAN-05001 when duplicating database from a consistent (cold) RMAN backup"},{"content":"Hi! I\u0026rsquo;m José Carlos.\nI am a data architecture enthusiast with a core focus on availability, performance, and automation. My career has been built on managing critical Oracle environments, but my technical curiosity has led me to specialize in the transition toward Cloud ecosystems and SRE (Site Reliability Engineering) culture.\nWhy this blog? This site serves as my personal “brain dump”: a place where I offload notes on complex diagnostics, automation scripts, and daily lessons learned. What started as a tool for my \u0026ldquo;future self\u0026rdquo; is now an open resource for the technical community.\nMy Current Stack Databases: Oracle (OCP), PostgreSQL, MongoDB. Infrastructure: AWS, OCI, Terraform. Philosophy: \u0026ldquo;Performance only matters if your database is UP!\u0026rdquo; Disclaimer Opinions: All opinions expressed on this blog are strictly my own and do not represent those of my employer. Technical Criteria: The procedures and recommendations described here are based on my own experience and criteria. They do not necessarily reflect the official methodology of vendors or my current employer. Responsibility: Please ensure you always test any script or configuration in a pre-production environment before applying it to mission-critical systems. ","permalink":"https://josecarlospavon.es/about/","summary":"\u003cp\u003eHi! I\u0026rsquo;m José Carlos.\u003c/p\u003e\n\u003cp\u003eI am a data architecture enthusiast with a core focus on \u003cstrong\u003eavailability, performance, and automation\u003c/strong\u003e. My career has been built on managing critical \u003cstrong\u003eOracle\u003c/strong\u003e environments, but my technical curiosity has led me to specialize in the transition toward \u003cstrong\u003eCloud ecosystems and SRE (Site Reliability Engineering) culture\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"why-this-blog\"\u003eWhy this blog?\u003c/h3\u003e\n\u003cp\u003eThis site serves as my personal \u003cstrong\u003e“brain dump”\u003c/strong\u003e: a place where I offload notes on complex diagnostics, automation scripts, and daily lessons learned. What started as a tool for my \u0026ldquo;future self\u0026rdquo; is now an open resource for the technical community.\u003c/p\u003e","title":"About"}]