Tuesday, 30 June 2026

Filled under:

 Here is a stronger, more current version you can use:

Database Reliability Engineer / SRE with strong experience across Oracle, PostgreSQL, and emerging database platforms, focused on reliability, resilience, automation, observability, and operational excellence.

Working as Scrum Master for the Emerging Database team, driving agile delivery, backlog refinement, sprint planning, blocker tracking, stakeholder alignment, and cross-functional coordination with engineers, Product Owners, Reliability Owners, and vendor teams.

Hands-on experience in Oracle and PostgreSQL operations, including performance diagnostics, query optimization, AWR/ADDM/Wait Event analysis, backup and recovery, Data Guard, RMAN, GoldenGate, Flashback, PITR, and HA/DR workflows.

Strong background in database SRE practices, including monitoring, alerting, incident reduction, automation of repetitive operational tasks, proactive risk identification, and continuous improvement of platform stability.

Contributing to observability initiatives by improving database visibility through metrics, dashboards, alerts, and reporting solutions that help teams identify issues earlier and reduce operational risk.

Experienced in business continuity and resilience activities, including BCM/BCP execution, failover readiness, recovery validation, evidence collection, and automation-led operational controls.

Designed and implemented automation solutions to reduce manual effort, improve consistency, minimize human error, and accelerate resolution of operational issues across database environments.

Actively involved in backup governance, patching support, RCA follow-ups, operational reporting, and capacity/performance reviews for mission-critical database platforms.

Applied data modelling, data mining, and ML/NLP-enabled analytical workflows to extract insights from structured and unstructured data, supporting ticketing workflow improvements and operational decision-making.

Collaborates closely with product managers, developers, engineering teams, and management stakeholders to translate technical issues into clear actions, risks, decisions, and delivery outcomes.

Brings a balanced mix of deep database engineering expertise, SRE mindset, agile delivery discipline, and stakeholder management to support reliable, scalable, and resilient data platforms.

You can remove the older/basic lines like “installation, configuration” and avoid repeating ML/NLP twice. This version sounds more aligned to Scrum Master + SRE + Observability + Current DBA/SRE work.

Posted By Nikhil06:07

Monday, 29 June 2026

Filled under:

 

Title:
AMR | Remove Persistence Settings from Lower Environment Clusters

Story:
As a developer,
I want to identify and remove unnecessary persistence settings such as AOF/RDB from AMR/Redis clusters in lower environments,
so that Dev/Test/UAT clusters do not incur unnecessary storage and I/O costs.

Description:
Persistence settings are currently enabled on some AMR/Redis clusters in lower environments. Since these environments may not require persistent storage for non-production workloads, the enabled persistence configuration can lead to additional storage and I/O cost.

This item is to analyze the impacted AMR/Redis clusters, confirm where persistence is not required, and remove/disable the persistence settings after validation. The activity should be aligned with the product/team requirements to avoid any impact to required testing or recovery scenarios.

Scope:

  • Identify AMR/Redis clusters where persistence settings are enabled.
  • Confirm impacted lower environments such as Dev, Test, and UAT.
  • Validate whether persistence is required for each cluster.
  • Remove/disable unnecessary AOF/RDB persistence settings.
  • Capture validation evidence after the change.

Acceptance Criteria:

  • Impacted clusters with persistence enabled are identified.
  • Confirmation is received that persistence is not required for selected lower environment clusters.
  • Persistence settings are removed/disabled where applicable.
  • Post-change validation is completed.
  • Evidence/comments are updated in the GitLab issue.

Posted By Nikhil01:59

Sunday, 28 June 2026

Filled under:

 

Hi Team, thanks everyone for joining.

As you all know, tomorrow is [Name]’s last working day with us. I wanted to set up this short catch-up so we can take a moment to thank him for his contributions, support, and collaboration with the team.

[Name], on behalf of the team, thank you for all your efforts and the value you have added. We really appreciate your support and wish you all the very best for your next opportunity.

I’ll keep this informal, so anyone who would like to share a few words or wishes, please feel free.

Posted By Nikhil23:22
Filled under:

 

Subject: Farewell Catch-up for [Name]

Hi Team,

As tomorrow is [Name]’s last working day with the team, setting up a short farewell catch-up to thank him for his contributions and wish him all the best for his next opportunity.

Please join if your schedule permits, so we can share our appreciation and give him a warm send-off.

Thanks,
Nikhil

Posted By Nikhil21:29

Wednesday, 24 June 2026

Filled under:

 Here is a professional version you can send as release notes:



---


Release Note 1

Issue Type: Enabler

Component: Cosmos DB

Change: Introduction of pipeline job to support Key Vault migration


The required pipelines have been updated to support Key Vault migration activities. This enables users to safely and consistently migrate keys from the infra-global subscription to their own subscription while ensuring impacted services are handled in a controlled manner.



---


Release Note 2

Issue Type: Enabler

Component: MongoDB vCore – TPAC Red Zone

Change: TPAC enablement for MongoDB vCore Red Zone


The TPAI pipeline has been updated to enable TPAC access for MongoDB vCore Red Zone. This change ensures that only authorized TPAC users can execute the pipeline and provide access in a controlled and compliant manner.



---


You can also write the email like this:


Hi Team,


Please find below the release notes for the latest changes:


[Paste the two release notes]


Please let me know if any further details are required.


Regards,

Nikhil

Posted By Nikhil22:48
Filled under:

 

Hi Microsoft Team,

Hope you are doing well.

We have not received the Minutes of Meeting for the call held on 18th. Could you please share the MoM when possible?

Thanks,
Nikhil

Posted By Nikhil07:37
Filled under:

 

Title: Validate AzureRmAlias removal impact for Emerging DB pipelines

User Story

As a developer, I want to validate the recent pipeline changes related to Enable-AzureRmAlias removal, so that we can confirm there is no impact on Emerging DB shared scripts, modules, or pipeline execution.

Background

Changes have been implemented to remove legacy Enable-AzureRmAlias usage and AzureRM module dependencies from common PowerShell scripts. Since these updates touch shared components, validation is required from the Emerging DB side before release sign-off.

Acceptance Criteria

  • Impact on Emerging DB pipelines is validated.
  • Shared scripts/modules used by Emerging DB are checked.
  • Any failures or required changes are documented.
  • Sign-off or feedback is shared for the upcoming release.

Posted By Nikhil05:07

Tuesday, 23 June 2026

Filled under:

 

Hi Hila, Vaishnavi,

Thanks Vaishnavi for the quick chat and for agreeing to discuss this further.

Setting up this call to discuss the LM9 validation inputs shared by Hila and to align on the next steps.

Agenda:

  • Review the inputs discussed with Hila
  • Understand Vaishnavi’s view and guidance
  • Align on any actions or follow-ups required

Thanks,
Nikhil

Posted By Nikhil07:38

Monday, 22 June 2026

Filled under:

 

I can read most of it. Some parts on the far right are cut off/unclear, so I’ve marked them as [text cut off / unclear].


Below is a high-level structure to illustrate what I mean. This still needs work. I’ve included some numbers that I have handy and placeholders (XX) where I don’t have them.

Current role

He has 2 major roles:

1. Site Reliability Engineer within the Database crew where he has multiple responsibilities:

  • Stability of Oracle and Postgres
    Environment size: 5300 Oracle DBs, 6200 Postgres DBs — 4100 Azure, 2100 on-prem
  • Technical escalation for complex and critical incidents
  • Problem management
  • Automation — aggregate the number of hours saved on BCM automation and other automations he’s written
  • Observability — leads the onboarding of over 5000 Oracle databases to LGTM
  • Mentors new joiners — mention how many he’s mentored and brought up-to-speed
  • Owns and evolves the backup and recovery strategy for Oracle databases

2. Scrum Master in the Emerging Database pod

Stepped up as a Scrum Master for the Emerging Database pod, which delivers the Redis Cache and Cosmos DB products. He drives agile execution across epics, improving delivery predictability and achieving a XX% increase in sprint velocity or reduction in cycle time. He ensures effective prioritization and alignment to organizational goals, combining technical expertise with delivery leadership to drive measurable outcomes at scale.


Contributions — What has he delivered and what was the impact?

Automation

  1. BCM automation — how many hours of manual effort avoided, feedback from BCM and number of app teams that showed appreciation.

  2. One of the pioneers for the Smart Ticket Handler, which used AI and machine learning, Reinfer and Nucleus, to classify user-raised incidents and provide automated responses and resolutions. This resulted in a 40% reduction of user-raised incidents for Oracle.

  3. Owned the actions for major platform migrations including Netcool to BigPanda and IPCenter to Amelia, successfully transitioning 100+ automations while ensuring continuity and alignment with new platforms.

  4. Other automations in Amelia.


Observability

  1. Successfully onboarded 400+ Oracle databases to LGTM. LGTM is one of the key dependencies for the re/write program, which is a major, GEB-level transformation initiative.

  2. Drives the remediation and resolution of deployment issues for Oracle through his technical knowledge and effective collaboration with stakeholders such as Automation Services and WMPC CTO.

  3. Contributes to the engineering discussion for the Postgres database exporter package that will enable the collection of metrics from Postgres databases.


Operational Efficiency

  1. Created several ServiceNow reports which improve visibility on open incidents, problems, service requests, and changes. Led to a XX% reduction in unassigned incidents during APAC shift hours.

  2. Created a backup reporting dashboard for Oracle that was used by the team globally, resulting in a XX% increase in successful backup completion.

  3. Authored over XX Assist portal articles and forms, which were integrated into the Smart Ticket Handler.


Technical Expertise and Core Operational Responsibilities

  1. Led the planning and execution of more than XX major APAC BCM events for databases. Partnered with BCM teams and stakeholders to validate readiness, coordinate execution, and ensure successful completion of events.

  2. Flawless execution of patching for critical XX Oracle and Postgres databases, including Mobile Pass, etc.


Principles and Behaviors

In addition to using this space to provide examples of how he demonstrated accountability with integrity, collaboration, etc., use this space for the culture and technical achievements beyond UBS.

  1. Oracle ACE — Being an Oracle ACE is widely regarded as prestigious in the tech industry. It is a global recognition initiative by Oracle that honors individuals who demonstrate exceptional expertise and consistently share their knowledge with the broader community.
    (lifted this from Google)

  2. Gold Certified Engineer

  3. AI Citizen — please confirm

  4. UBS Stack Overflow contributor — answered XX number of questions and awarded XX badges

  5. He has an Oracle blog

  6. Was he part of the Hackathon year where you guys placed in the semi-finals?

  7. Enumerate all the charity and community events that he’s led, joined, or contributed to.

Posted By Nikhil23:03
Filled under:

 

Hi All,

A quick clarification on the earlier communication regarding the Cosmos DB CMK / Key Vault remediation.

The email was sent to a wider audience for awareness and visibility. However, action is required only for Cosmos DB accounts using Customer-Managed Keys where remediation/migration is still pending.

If your Cosmos DB account has already been migrated/remediated, or if this change is not applicable to your setup, no further action is required from your side.

For accounts where remediation is still pending, please review the shared guidance and proceed with the appropriate remediation option before the communicated deadline.

Thanks for your understanding.

Regards,
Emerging Databases Team

Posted By Nikhil22:24
Filled under:

 

Use these prompts directly in Teams Copilot.

Middle of the meeting

Type:

Summarize the discussion so far and list any blockers, open questions, decisions, and action items mentioned.

For Scrum/refinement/planning calls, use:

Summarize the discussion so far. Identify any items that need clarification, risks/blockers, ownership gaps, and follow-up actions.

For vendor/Microsoft calls, use:

Summarize the discussion so far. Capture any commitments, dependencies, pending answers, owners, and expected timelines.

Last 5 minutes

Type:

Create a closing summary with key decisions, action items, owners, due dates, blockers, and next steps.

For Scrum Master use, this is even better:

Prepare a clear meeting closure summary. Include: decisions made, action items with owners, unresolved blockers, dependencies, due dates, and topics to carry forward.

Then you can say verbally:

Before we close, I’ll quickly confirm the decisions, action items, owners and next steps so we are aligned.

A very strong final prompt for your role:

Generate professional meeting notes from this call with sections: Summary, Decisions, Action Items, Owners, Blockers, Dependencies, Due Dates, and Next Steps.

Posted By Nikhil20:13
Filled under:

 

Hi, my name is Nikhil Kotak. I have been with UBS for more than nine years, and I currently work as a Site Reliability Engineer for databases. I also support the Emerging Database team as Scrum Master.

One achievement I am especially proud of is contributing to reliability and delivery maturity in the Emerging Database space. Emerging Database involves evolving technologies, external dependencies and new ways of working, where clarity, ownership and structured execution are very important. As Scrum Master, I help convert unclear topics into trackable actions, surface blockers early, align engineers, Product Owners, Reliability Owners and vendor teams, and keep delivery focused on outcomes.

Alongside this, I am proud of my contribution to PostgreSQL reliability since PostgreSQL was introduced as a strategic database platform within the bank. I conducted brown bag sessions with stakeholders across APAC and EMEA to build awareness, confidence and alignment. I also independently designed PostgreSQL BCM automation, converting manual checks, risk controls and evidence collection into a repeatable automated process, reducing manual effort by around 95%.

I have also been involved in ML and AI-led automation initiatives, using intelligent automation to reduce repetitive manual ticket resolution and improve operational efficiency by around 22% over the past year.

What motivates and inspires me at UBS is the scale, trust and impact of the work. I am proud to be recognized internally through CE Gold, externally by Oracle as an ACE Pro, and to contribute to UBS volunteering events. These experiences motivate me to keep growing, sharing knowledge and contributing beyond my immediate role.

Overall, I am proud to contribute through reliability, automation, collaboration, volunteering and continuous improvement.

Posted By Nikhil00:22

Sunday, 21 June 2026

Filled under:

Dhirendra

 BBS right for Mongo  - to scrap

+

AC22 - change ownership & how to rotate password


Upcoming

Vulnerability - Python, Azure CLI and __

Change the name of EPIC - make just "IDB migration to secure sharepoint"


to do

- Maintianance scope to scrap and

Other epic refinement

Posted By Nikhil06:02

Pitch for recording (Sunday)

Filled under:

90-second memory cue

  1. Intro
    Nikhil Kotak — Database SRE — Scrum Master for Emerging DB.

  2. Proud achievement
    PostgreSQL BCM automation.
    Manual checks → repeatable automation.
    Supported BCM BigRock events.
    Reduced manual effort by around 95%.
    Improved reliability, auditability and confidence.

  3. What motivates me at UBS
    Scale and impact of work.
    Small reliability improvements protect important business services.
    Opportunity to work with engineers, POs, ROs and management.
    Technical depth + delivery ownership.

  4. Favourite app
    LinkedIn.
    Learning, sharing, technology community, industry trends.
    Supports my growth mindset.

  5. Closing
    Proud to contribute through reliability, automation, collaboration and continuous improvement.


##################################################################################

 

Hi, my name is Nikhil Kotak. I currently work as a Site Reliability Engineer for databases, and I also support the Emerging Database team as Scrum Master.

One achievement I am especially proud of is my contribution to PostgreSQL reliability since PostgreSQL was introduced as a strategic database platform within the bank. During that phase, I also conducted brown bag sessions with stakeholders across APAC and EMEA to build awareness, confidence and alignment around the platform.

I then independently designed and developed PostgreSQL Business Continuity Management automation. This converted manual validation, high-availability checks, risk controls and evidence collection into a repeatable automated process. The automation supported multiple BCM BigRock events across Oracle and PostgreSQL databases and helped reduce manual effort by around 95%. I am proud of this because it improved reliability, consistency, auditability and confidence during critical continuity events.

I have also been involved in ML and AI-led automation initiatives, where we used intelligent automation to reduce repetitive manual ticket resolution and improve operational efficiency. This helped reduce manual resolution effort by around 22% over the past year.

What motivates and inspires me at UBS is the scale, trust and impact of the work. Having been with UBS for more than nine years, I have seen how reliability, discipline and continuous improvement directly support important business services.

In database reliability, improvements can protect important business services.. I am inspired by the opportunity to work with engineers, Product Owners, Reliability Owners and stakeholders, where I can combine technical depth, automation and delivery ownership to create reliable outcomes.

My favourite app is LinkedIn. For me, it is more than a networking app. It helps me learn from the technology community, share knowledge, follow industry trends and stay connected with experts across databases, cloud and AI.

Overall, I am proud to contribute through reliability, automation, collaboration and continuous improvement.

Posted By Nikhil03:51

Saturday, 20 June 2026

Filled under:

 My role sits

I work across

Over the recent period,

One of my key individual contributions has been PostgreSQL Business Continuity Management

.. contribution n numbers

Another important contribution has been in Oracle and LGTM onboarding

 s Scrum Master for the Emerging Database team, my contribution is not limited to meeting facilitation. I bring technical understanding into delivery discussions


From a Principles and Behaviors perspective, I try to demonstrate collaboration, growth, innovation and transformation in practical ways. I collaborate with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders to translate technical topics into clear actions. I support growth through certifications, technical blogging, knowledge sharing and mentoring new joiners. I innovate by converting manual, repetitive and evidence-heavy activities into automation. I support transformation by improving transparency, structured tracking and early risk visibility.


I have also been recognized by Oracle through its ACE community program for my technical contributions. This gives me exposure to Oracle product direction, new features and wider industry practices, which I can bring back into the organization.


Overall, I believe my impact goes beyond completing assigned tasks. I have taken ownership of complex and evolving areas, delivered measurable reliability improvements, supported team delivery, and contributed to better ways of working. These are the areas where I believe I am already demonstrating the ownership, maturity and wider influence expected at the target level.


--------------



“Reduced manual effort by around 95%, while improving consistency, auditability and confidence during critical events.”


_----------------------



Hi, my name is [Your Name]. I work as a Database Reliability Engineer / Site Reliability Engineer, and I also perform Scrum Master responsibilities for the Emerging Database team.

My role sits at the intersection of database reliability, operational resilience, automation and delivery coordination. I work across enterprise database technologies including Oracle, PostgreSQL and Emerging Database platforms, supporting production stability, business continuity readiness, backup governance, patching, automation and operational reporting.

Over the recent period, I have taken ownership of responsibilities beyond my core role, particularly in PostgreSQL Site Reliability Engineering and Scrum Master activities for the Emerging Database team. These areas require technical judgement, ownership, stakeholder coordination and the ability to bring structure to evolving topics.

One of my key individual contributions has been PostgreSQL Business Continuity Management automation. When PostgreSQL was introduced into the bank environment, I built strong engineering knowledge in this area and used that experience to design and develop automation for continuity events.

This work converted manual high availability checks, validation steps, risk controls and evidence requirements into a repeatable and consistent process. The automation has supported more than 7 business continuity events across a large database estate, including 200+ Oracle databases and 40+ PostgreSQL databases. It has reduced manual effort by around 95%, while improving consistency, auditability and confidence during critical events.

Another important area I have contributed to is improving operational visibility and observability across the database estate. My focus has been on making issues easier to detect, track and act upon by converting fragmented checks and manual follow-ups into more structured reporting and automation. This improves transparency for engineers and stakeholders, supports faster decision-making, and creates a stronger foundation for future enhancements around proactive monitoring, trend analysis and reliability insights.

I have also contributed to AI and ML-driven initiatives where automation was used to improve operational efficiency. By applying automation and intelligence-driven approaches to recurring support patterns, we reduced manual ticket resolution effort by around 22% over the past year. This reflects my focus on not just resolving issues, but improving the way issues are identified, routed and handled over time.

As Scrum Master for the Emerging Database team, my contribution is not limited to meeting facilitation. I bring technical understanding into delivery discussions, help clarify ambiguous work, surface blockers early, and keep the team focused on outcomes and accountability. I see this as an important bridge between engineering detail and business priorities.

From a Principles and Behaviors perspective, I try to demonstrate collaboration, growth, innovation and transformation in practical ways. I collaborate with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders to translate technical topics into clear actions. I support growth through certifications, technical blogging, knowledge sharing and mentoring new joiners. I innovate by converting manual, repetitive and evidence-heavy activities into automation. I support transformation by improving transparency, structured tracking and early risk visibility.

I have also been recognized by Oracle through its ACE community program for my technical contributions. This gives me exposure to Oracle product direction, new features and wider industry practices, which I can bring back into the organization.

Overall, I believe my impact goes beyond completing assigned tasks. I have taken ownership of complex and evolving areas, delivered measurable reliability improvements, improved observability and operational visibility, supported team delivery, and contributed to better ways of working. These are the areas where I believe I am already demonstrating the ownership, maturity and wider influence expected at the target level.

Posted By Nikhil05:55
Filled under:

 

Hi, my name is [Your Name]. I am currently working as a Database Reliability Engineer / Site Reliability Engineer, with additional responsibilities as Scrum Master for the Emerging Database team.

My role is focused on database reliability, operational resilience, automation and platform stability. I work across enterprise database technologies including Oracle, PostgreSQL and Emerging Database platforms. In this role, I contribute to production reliability, business continuity readiness, database automation, patching support, backup governance, operational reporting and cross-team coordination.

Over the last period, I have also stepped into wider responsibilities in two important areas: PostgreSQL Site Reliability Engineering and Scrum Master responsibilities for the Emerging Database team. These areas require technical judgement, ownership, stakeholder alignment and the ability to bring structure where topics are still evolving.

One of my key individual contributions has been PostgreSQL Business Continuity Management automation. I designed and developed this using my own PostgreSQL engineering knowledge, built from the time PostgreSQL was introduced within the bank environment. I converted high availability checks, validation steps, operational risks and evidence requirements into repeatable automation.

This automation has supported more than 7 business continuity events, covering 200+ Oracle databases and 40+ PostgreSQL databases, and has reduced manual effort by around 95%. More importantly, it has improved consistency, auditability and confidence during critical continuity events.

Another important area I contributed to is Oracle / LGTM onboarding. I analysed blockers related to standard ID and certificates, identified recurring host-level issues and helped convert fragmented failures into structured remediation actions. This helped move the work from reactive troubleshooting to more systemic resolution.

As Scrum Master for the Emerging Database team, my contribution goes beyond routine facilitation. I bring technical understanding into delivery discussions, help clarify ambiguous work, surface blockers early, and keep focus on outcomes and accountability. I see this as an important bridge between engineering detail and business priorities.

From a Principles & Behaviors perspective, I try to demonstrate collaboration, growth, innovation and transformation in practical ways. I collaborate with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders to translate technical topics into clear actions and decisions. I support growth through certifications, technical blogging, knowledge sharing and by acting as a buddy or mentor for new joiners. I innovate by converting manual, repetitive and evidence-heavy activities into automation. I help transform the way we work by improving transparency, structured tracking and early risk visibility.

I have also been recognized by Oracle through its community / ACE program for my technical contributions. This gives me exposure to Oracle product direction, new features and industry practices, which I can bring back into the organization.

Overall, I believe my impact is not limited to completing assigned tasks. I have taken ownership of complex and evolving areas, delivered measurable reliability improvements, supported team delivery and contributed to better ways of working. These are the areas where I believe I am already demonstrating the ownership, maturity and wider influence expected at the target rank.

Posted By Nikhil04:04

Friday, 19 June 2026

Filled under:

 

Based on the refined input, you can restructure the mail like this so it is clearer and action-oriented.


Subject: Action Required: Cosmos DB CMK Key Vault Access Update – Remediation Options

Dear User,

We are notifying you of an important update regarding encryption key management for your Cosmos DB account(s) using Customer-Managed Keys (CMK) within the UBS Prod tenant.

As per the latest Azure changes, the way Azure Key Vaults are accessed by Cosmos DB is changing. This impacts Cosmos DB accounts using CMK, regardless of whether the Key Vault is centrally managed or maintained within your own subscription.

To avoid service impact, the required remediation must be completed by December 2026.

Impact if no action is taken:
If the required action is not completed before the deadline, the affected Cosmos DB account may enter a failure state and become inaccessible.

Available Remediation Options

Please review and choose one of the following options based on your application setup and ownership model:

Option A: Create a new Key Vault and update Cosmos DB with the new Key Vault URI
This option allows you to continue using CMK by moving the encryption key to a Key Vault managed within your subscription and updating the Cosmos DB configuration with the new keyVaultKeyUri.

High-level steps:

  1. Create a new Key Vault with:

    • Soft Delete enabled
    • Purge Protection enabled
    • Valid RSA key of minimum 3072 bits
  2. Grant Cosmos DB access to the new Key Vault:

    • Assign permissions to the Cosmos DB managed identity
    • Required permissions: get, wrapKey, unwrapKey
    • Alternatively, assign the RBAC role: Key Vault Crypto Service Encryption User
  3. Update Cosmos DB to use the new Key Vault key URI.

  4. Allow Cosmos DB to complete the encryption key transition.

  5. Validate:

    • Read/write operations
    • customerManagedKeyStatus
    • Alerts/logs

Option B: Create a new Cosmos DB account with Microsoft-Managed Keys (MMK) and migrate data
Create a new Cosmos DB account configured with Microsoft-Managed Keys and migrate data from the existing CMK-enabled account using container copy.

Option C: Create a new Cosmos DB account using Point-in-Time Restore with MMK configuration
Create a new Cosmos DB account using Point-in-Time Restore and configure the restored account with Microsoft-Managed Keys.

Required Action

Please confirm which remediation option you would like to proceed with for your Cosmos DB account(s). Once confirmed, the Emerging Databases team can guide you on the next steps and required coordination.

For any questions or assistance, please reach out to DL-TS-HS-DB-EMERGINGDB-ENG.

Thanks & Regards,
Emerging Databases Team

Posted By Nikhil03:57
Filled under:

 

Subject: Q3 Objectives Alignment – Emerging DB

Hi Team,

Setting up this call to align on the Q3 objectives for Emerging DB, review key priorities, clarify scope/ownership, and identify any dependencies or blockers early.

Agenda:

  • Review proposed Q3 objectives
  • Align on priorities and expected outcomes
  • Identify dependencies, risks, and ownership
  • Confirm next steps for planning/tracking

Thanks,
Nikhil

Posted By Nikhil03:10
Filled under:

 

Posted By Nikhil00:40

Thursday, 18 June 2026

Filled under:

 

Question 3: Principles & Behaviors

Candidate demonstrates ownership, collaboration, growth mindset, innovation and transformation through a reliability-first approach.

Role-model behaviors include:

  • Collaborate: Works effectively with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders to translate technical issues into clear actions, risks and decisions.
  • Growth: Builds technical depth through certifications, blogging and Oracle community involvement, while also mentoring new joiners as a buddy to help them understand processes, team practices and operational expectations.
  • Innovate: Independently designed PostgreSQL BCM automation and improved operational checks by converting manual, repetitive and evidence-heavy activities into reliable automated processes.
  • Transform: Helps move the team from reactive issue handling to structured tracking, early blocker visibility and outcome-focused delivery.
  • Accountability: Takes ownership of unclear and evolving areas, including PostgreSQL reliability automation and Emerging Database Scrum Master responsibilities.
  • Leadership: As Scrum Master, balances empathy with accountability, creates transparency and brings a technical lens that connects engineering details with business priorities.
  • External recognition: Recognized by Oracle through its community / ACE program for technical contributions, providing exposure to Oracle product direction, new features and industry practices that can be brought back into the organization.

These behaviors demonstrate maturity beyond routine execution and align with the target-rank expectations of collaboration, growth, innovation and transformation.

Posted By Nikhil18:54
Filled under:

 

Question 3: Principles & Behaviors

Candidate stands out as a role model through ownership, collaboration, learning agility and a reliability-first mindset.

Candidate demonstrates ownership by taking responsibility for unclear or evolving areas, including PostgreSQL reliability automation and Scrum Master responsibilities for the Emerging Database team. These areas require more than routine execution; they require judgement, structure, confidence and the ability to guide others through ambiguity.

Candidate collaborates effectively across engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders. Candidate helps translate technical issues into clear actions, ensures blockers are visible early and supports practical decision-making. This reflects strong collaboration and the ability to influence without relying only on formal authority.

As Scrum Master, candidate creates a transparent and constructive environment where engineers can raise risks early while still maintaining focus on commitments and delivery outcomes. Candidate balances empathy with accountability and brings a technical lens that connects engineering details with business priorities.

Candidate also demonstrates growth and innovation through automation, technical learning, certifications, blogging and knowledge sharing. These behaviors show commitment to continuous improvement and willingness to bring learning back into the organization.

Overall, candidate demonstrates the target-rank behaviors of collaboration, innovation, transformation, mobility and growth.

Posted By Nikhil18:41
Filled under:

 

How to Deliver It Without Sounding Robotic

Don’t memorize the full script word by word. Keep this cue card near the camera:

1. Role
SRE / DBRE + Scrum Master

2. Reliability
Automation, resilience, stability

3. Impact
BCM, LGTM, health checks, backup reporting, governance

4. Scrum Master value
Clarity, blockers, accountability, technical understanding

5. Strengths
Ownership, learning, collaboration, follow-through

6. Closing
Improve reliability and delivery maturity


Camera-Shy Recording Method

Record in 6 small parts, then merge if allowed. This is much easier than doing one perfect take.

Part 1: Introduction
Part 2: Current role
Part 3: Contributions
Part 4: Scrum Master value
Part 5: Learning and strengths
Part 6: Closing

Speak slowly. A 3–4 minute video should feel slightly slower than normal conversation. Pause after each paragraph. Pauses look confident.

Use this tone: calm, sincere, prepared — not dramatic, not overly energetic.

Before recording, say this twice:

“I don’t need to sound perfect. I only need to sound clear, sincere and structured.”

That mindset will help your delivery.

Posted By Nikhil09:03

Shorter 3-Minute Version

Filled under:

 


Use this if you feel the above is too long:

Hi, I am Nikhil. I currently work as a Site Reliability Engineer / Database Reliability Engineer, and I also support the Emerging DB POD as Scrum Master.

My role is focused on database reliability, automation, operational resilience and platform stability. I work across Oracle, PostgreSQL and emerging database technologies such as Cosmos DB, Redis, MongoDB and DocumentDB.

In my view, reliability is not only about fixing issues. It is also about identifying patterns, reducing repeat problems, improving visibility and converting manual work into structured and repeatable solutions.

Some areas where I have contributed include PostgreSQL BCM automation, Oracle and LGTM onboarding support, standard ID remediation analysis, database health-check automation, backup reporting improvements and governance tracking. These contributions helped reduce manual effort, improve evidence collection, strengthen BCM readiness and bring better visibility to operational risks.

What I try to bring into my work is ownership. When I see an issue, I try to understand whether it is just a one-time problem or part of a wider gap. If there is a pattern, I try to convert it into an improvement action, automation opportunity or better tracking process.

As a Scrum Master, I see my contribution beyond running ceremonies. I use my technical background to bring clarity to discussions, help surface blockers early, and support outcome-focused conversations. Because I understand the database engineering side, I can help connect technical challenges with delivery priorities and stakeholder expectations.

I also try to create a transparent and constructive environment where people can raise risks early, while still keeping the focus on accountability and practical next steps. I believe this balance of empathy, clarity and ownership is important for any team.

Continuous learning is also very important to me. Certifications, technical blogging and involvement in the database community have helped me improve my technical depth and confidence. I try to bring that learning mindset into my daily work and share knowledge where possible.

I would describe myself as dependable, curious, collaborative and improvement-focused. I may not always be the loudest person in the room, but I believe in preparation, consistency and follow-through.

Overall, I see my contribution as a mix of technical reliability, automation mindset, structured delivery support and collaborative leadership. My goal is to continue improving platform stability, reducing manual effort, supporting the team better and contributing to the organization with stronger impact.

Thank you.

Posted By Nikhil09:02
Filled under:

#####################

Question 1: Current Role

The candidate is currently working as a Site Reliability Engineer and Scrum Master for the Emerging Database team, contributing to database reliability, automation, operational resilience and platform stability across enterprise database technologies.

The role includes individual ownership across:

  • Production reliability, business continuity readiness and operational resilience.

  • Database automation, patching support, backup governance and operational reporting.

  • PostgreSQL Site Reliability Engineering responsibilities.

  • Scrum Master responsibilities for the Emerging Database team.

  • Coordination with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders.

The candidate stepped into PostgreSQL SRE responsibilities when PostgreSQL was introduced as a strategic database platform within the bank. More recently, the candidate also took on Scrum Master responsibilities for Emerging Database, covering areas previously handled or supported by individuals operating at the desired rank.

As Scrum Master, the candidate’s contribution goes beyond routine facilitation. They bring technical understanding, delivery discipline and stakeholder management to create clarity, surface risks early, convert unclear issues into trackable actions and improve delivery transparency.

This demonstrates target-rank behavior by combining hands-on engineering depth with broader ownership, cross-team influence and delivery accountability.

Candidate has been in this role since: [add month/year]


Question 2: Contribution and Impact

The candidate has delivered strong individual impact across reliability, automation and operational maturity.

Key contributions include:

  • Independently designed and developed PostgreSQL BCM automation using deep PostgreSQL engineering knowledge built since PostgreSQL was introduced within the bank.

  • Supported 7+ BCM BigRock events through automation coverage across 200+ Oracle databases and 40+ PostgreSQL databases.

  • Reduced BCM manual effort by approximately 95% through automated validation, execution support and evidence collection.

  • Converted PostgreSQL HA checks, validation points, operational risks and evidence requirements into repeatable automation.

  • Analysed Oracle/LGTM onboarding blockers related to standard ID and certificates, identified recurring host-level issues and drove structured remediation actions.

  • Improved database health checks, backup reporting and operational tracking for audit and governance needs.

  • Applied technical judgement as Scrum Master to clarify ambiguous work, expose blockers early, manage dependencies and keep delivery focused on outcomes.

These contributions improved BCM consistency, auditability, risk visibility and confidence during continuity events.

The candidate’s impact is comparable to the next rank because they independently own complex areas, solve systemic issues and influence delivery beyond assigned technical tasks.


Question 3: Principles & Behaviors

The candidate demonstrates ownership, collaboration, learning agility and a reliability-first mindset.

Role-model behaviors include:

  • Takes ownership of unclear and evolving areas, including PostgreSQL reliability automation and Emerging Database Scrum Master responsibilities.

  • Translates technical issues into clear actions, risks and decisions.

  • Collaborates effectively with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders.

  • Creates transparency by surfacing blockers early and keeping focus on commitments and outcomes.

  • Balances empathy with accountability while supporting a constructive team environment.

  • Uses technical judgement to connect engineering details with business priorities.

  • Drives continuous improvement through automation, certifications, technical blogging and knowledge sharing.

  • Recognized by Oracle through its community/ACE program for technical contributions, providing early exposure to Oracle product direction, new features and industry practices that can be brought back into the organization.

  • Transforms manual, repetitive and evidence-heavy operational work into reliable automated processes.

These behaviors show maturity beyond routine execution. The candidate demonstrates target-rank expectations through collaboration, innovation, transformation, mobility and growth, while consistently contributing to team reliability and delivery outcomes.

Posted By Nikhil08:56

Monday, 15 June 2026

Filled under:

 

Hi [PO Name], this ask is part of the UBS Model Identification process to confirm whether our applications qualify as a model under the model governance policy.

Based on the details, Azure Cache for Redis and Azure Cosmos DB are infrastructure/data storage services. Redis is used for caching, and Cosmos DB is a managed NoSQL database service. They do not themselves perform prediction, scoring, forecasting, risk calculation, optimization, or decision-making.

So our product appears to fall under application/database infrastructure and should not qualify as a model candidate. We can affirm the portal details with this justification.

Posted By Nikhil03:44

Friday, 12 June 2026

Filled under:

 Hi Team, sharing a quick update from today’s BCM event — all PostgreSQL BCM activities have been completed successfully.


This time, the PostgreSQL switchover/switchback was executed via automation, and all validations were successful. Thanks everyone for the support.

Posted By Nikhil23:08

Thursday, 11 June 2026

Filled under:

 We are currently working on LGTM deployment, where the deployment activity involves certificate installation on the target hosts.

The deployment was successful in the Development environment. However, for Production and TE2 environments, the deployment did not proceed directly as it went for approval. To avoid approval dependency, the required hosts were whitelisted under reference number: .

Even after whitelisting the hosts, the deployment still went for approval. We have now scheduled a call with the CREDS team to understand what additional configuration or mapping is required.

As per the available FAQ, the technical account may also need to be mapped in ISAAC for the deployment to proceed without approval. We need support to confirm the complete requirement and identify what is currently missing, so that future LGTM deployments to Production and TE2 can proceed without manual approval for this account.

Request:

Please help review the current setup and confirm:

Whether the host whitelisting has been correctly applied.

Whether the technical account needs to be mapped in ISAAC.

Any additional approval bypass configuration required for Production and TE2.

What changes are needed so that LGTM certificate deployment can proceed without approval for this account. :::

A shorter title could be:

LGTM deployment going for approval despite host whitelisting

Posted By Nikhil01:37

Wednesday, 10 June 2026

Filled under:

 Here is a clean 2–3 line release summary for each item:

:::writing{variant="document" id="73924"} 1. Policy to disable HA for lower environments — Audit Mode

Introduced an audit-mode policy to identify HA-enabled instances across AMR, Redis, Cosmos DB, and DocumentDB in dev/test environments. This will help review unnecessary HA usage in lower environments and support future cost-optimization actions.

2. Azure Cosmos — ICC Evidence Document Update

Updated the Azure Cosmos ICC evidence documentation with the latest required evidence triggered by MERs. This ensures the relevant compliance artefacts remain current and aligned with ICC requirements.

3. Cosmos — Prod Database Refresh Script

Developed a script to copy required metadata from production to lower environments. This helps provide a more production-like setup in non-prod, improving testing reliability and validation quality.

4. Azure Cosmos vCore & AMR — Migration to Python / AKS Analysis

Completed analysis to support role assignment for Azure Cosmos vCore and Azure Managed Redis using a Python-based application approach. This is a step towards enabling Azure Function-based execution and reducing dependency on ADO pipelines.

5. Automation Solution for Pipeline Failure — Analysis

Performed analysis for improving the solution design around pipeline failure detection. The objective is to reduce false positives and improve identification of actual pipeline failures.

6. Agent Pool Fix — Invoke Pyfunc Pipeline

Worked on the agent pool fix required for the Invoke Pyfunc pipeline execution. This helps improve pipeline stability and ensures smoother automation runs. :::

Posted By Nikhil22:14
Filled under:

 We have one hour blocked, but if we are able to cover previous action items, today’s feedback, and agree on next actions earlier, we can close early.”

Thanks, lets now move to this iteration’s retro and capture fresh inputs on what went well, what did not go well, and what we can improve.”

----

Hi Team, thanks for joining. We’ll use this retro to quickly review the previous action items, then capture inputs for this iteration — what went well, what did not go well, and what we can improve. We don’t need to use the full hour if we finish early.

Before we start fresh inputs, let’s quickly revisit the takeaways from the previous retro and check whether we saw any improvement.”

Then close

Thanks, I’ll carry forward only the items that still need action. Let’s now move to this iteration’s retro inputs.”

Then for 10mins

Ending

Thanks everyone for the inputs. I’ll summarize the key points and action items after the call. We’ll review progress on these in the next retro.”

“We have covered the main points and actions, so we can give some time back. Thanks everyone.”

Posted By Nikhil20:04
Filled under:

 

Hi Team,

This request has been assigned to DBA for running a query on application tables.

Could you please confirm if the expectation is really for DBA to execute this? As per usual controls, DBAs should not run application-level queries using privileged access on application-owned tables.

It looks like this may have been assigned to DBA a bit too quickly, so checking before we proceed.

Please confirm the application owner and the approved account/process to run this query.

Regards,
Nikhil

Posted By Nikhil09:21
Filled under:

 

Title: Standard ID Remediation for Oracle LGTM Onboarding in Lower Environments

As a DBA / SRE working on Oracle LGTM onboarding,
I want to identify and remediate Standard ID related issues on lower environment Oracle hosts,
So that SRVAPD account deployment can complete successfully and LGTM onboarding can continue without repeated failures.


Background

As part of the LGTM onboarding activity, we are currently working on Oracle databases. After completing a few batches, we started seeing failures during the deployment of the SRVAPD account.

Initial investigation showed that the failures were not related to the LGTM onboarding flow itself, but were caused by underlying Standard ID issues on several lower environment servers.

The following issues were observed across different hosts:

  • Standard ID was in a broken state.
  • Standard ID details were missing from the expected source.
  • Standard ID certificate was expired on some hosts.
  • Pisa package related issues were also seen on a few servers.

Based on the investigation, we decided to segregate the issues by category, identify the ones with major weightage, and start remediation for the most common and high-impact cases first.


Scope of Work

  • Identify lower environment Oracle hosts impacted by Standard ID issues.
  • Segregate the failures based on the type of issue observed.
  • Validate hosts where SRVAPD deployment failed due to Standard ID problems.
  • Perform trial remediation on selected hosts.
  • Develop a script to remediate Standard ID issues.
  • Add required validations in the script to confirm the remediation is successful.
  • Test the script on multiple hosts before wider rollout.
  • Work with the automation team to deploy the script through Amelia.
  • Use Amelia automation to remediate lower environment hosts.

Acceptance Criteria

  • Affected hosts are identified and categorized based on the Standard ID issue.
  • Major failure patterns are separated from one-off host-specific issues.
  • Trial remediation is completed successfully on selected hosts.
  • Remediation script is developed and tested.
  • Script performs required pre-checks and post-checks.
  • Script is deployed through Amelia automation.
  • Lower environment hosts can be remediated using Amelia.
  • SRVAPD account deployment is revalidated after remediation.
  • Remediated hosts are ready to continue with LGTM onboarding.

Comments / Checklist

  • [ ] Identified that SRVAPD account deployment started failing after a few LGTM onboarding batches.
  • [ ] Investigated and confirmed that multiple lower environment servers had Standard ID in a broken state.
  • [ ] Observed cases where Standard ID details were missing from the required source.
  • [ ] Observed cases where Standard ID certificates were expired.
  • [ ] Observed cases where Pisa package related issues were present.
  • [ ] Segregated the issues based on failure category and impact.
  • [ ] Performed trial remediation on various hosts to validate the fix.
  • [ ] Developed a remediation script for Standard ID related issues.
  • [ ] Tested the script on multiple hosts to ensure it works as expected.
  • [ ] Added validations in the script to confirm Standard ID status before and after remediation.
  • [ ] Worked with the automation team to deploy the script in Amelia.
  • [ ] Plan to use Amelia automation for lower environment remediation.
  • [ ] Revalidate SRVAPD deployment and LGTM onboarding after remediation.

Posted By Nikhil07:40
Filled under:

 SET LINESIZE 300

SET PAGESIZE 50000

SET LONG 1000000

SET LONGCHUNKSIZE 1000000

SET TRIMSPOOL ON

SET WRAP ON


COLUMN hostname FORMAT A45

COLUMN script_result FORMAT A200

Posted By Nikhil07:34
Filled under:

INSERT ALL

  INTO host_check_table (hostname) VALUES ('server01')

  INTO host_check_table (hostname) VALUES ('server02')

  INTO host_check_table (hostname) VALUES ('server03')

SELECT 1 FROM dual;


COMMIT;



UPDATE your_table_name

SET details = NULL

WHERE hostname = 'server02';


COMMIT;



SELECT hostname, details
FROM your_table_name
WHERE hostname = 'server02';




SET LONG 1000000

SET LONGCHUNKSIZE 1000000

SET LINESIZE 300

COLUMN script_result FORMAT A200

Posted By Nikhil07:13
Filled under:

 

Hi Team,

We have raised the change for deploying the new policies, however this time the SDLC Release Checker has marked it as Not Compliant with the reason that no release is registered in SBC for the AA number.

In our previous similar changes, we do not recall receiving this specific task/validation requirement. Could you please help confirm if there has been any recent process change, or if any additional release registration is now required before this change can proceed?

Please also advise the next steps to make this change compliant.

Thanks,
Nikhil

Posted By Nikhil04:54

Tuesday, 9 June 2026

Filled under:

 

Hi Sudhanshu,

Hope you are doing well.

As part of the Emerging DB discussions, we have biweekly sync calls with Microsoft. I will be taking up Anjali’s role for the time being, so could you please include me in the upcoming meeting invites, email conversations, and MOM/action item updates going forward?

This will help me stay aligned on the ongoing discussions, pending action items, and follow-ups.

Thanks,
Nikhil

Posted By Nikhil07:08

Monday, 8 June 2026

Filled under:

 Policy, fix, compliance, and optimization items are progressing across AMR, Redis, Cosmos, DocumentDB, and Mongo DB vCore. Multiple policy updates are awaiting release, including TLS support, audit policy assignment, and audit-to-deny policy changes. Fixes related to TPAC access, ADO agent pool access, and Cosmos ICC evidence capture are in progress or testing. Optimization items to block expensive Redis Enterprise modules and support cost optimization through audit policy additions are also progressing.

Posted By Nikhil04:07

Sunday, 7 June 2026

Filled under:

 I would like to appreciate Ranjit for the way he leads and supports the team.


He brings new ideas, keeps everyone aligned, and ensures every team member gets the right guidance, learning opportunity, workload balance, and recognition. He also spends time understanding each person’s activities, velocity, and blockers to ensure proper coverage across the team.


He always appreciates team members’ achievements in every aspect and makes sure good work is recognized fairly.


Even while handling management responsibilities, he continues to support Sybase and MSSQL operations wherever required in APAC, which is truly inspiring.


Thank you, Ranjit, for your continued guidance, support, and leadership.

Posted By Nikhil07:08
Filled under:

 

Hi Team, quick update — LGTM onboarding was earlier halted due to Standard ID cert mismatch/unavailability.

The remediation steps and script we prepared have been tested on the previous batch, and the script is now with Automation team for module deployment.

Once the module is live, the plan is to remediate all non-prod hosts and proceed with LGTM onboarding once remediation is completed. Attaching the old target reference for tracking.

Posted By Nikhil06:28

retro call

Filled under:

start :

“Hi Team, we’ll do a quick retro for the last two iterations. Please add your inputs under what went well, what did not go so well, and what we can do differently. After that we’ll quickly discuss and capture 2–3 improvement actions.”

Let’s keep it open and constructive. This is mainly to improve our process, coordination, blockers, and delivery flow.”


--------------###############################################-------------------

Step :1 


“Hi Team, we’ll do a quick retro for the last two iterations. 

Before we add new retro points, let’s quickly revisit the improvement areas from last retro and check whether we improved, stayed the same, or still need action.”

From last retro, we had points around time-boxing, external dependencies, access delays, Red Zone visibility, and documentation process. Did we see improvement in these areas this iteration 


Which of these are still recurring and should become action items for next iteration?

or

“Did we improve on this, or is this still recurring?”


------------------------------------------------------------------------------------------------------------

Step :2

“Thanks, let’s now move to today’s retro board and capture fresh inputs for this iteration.”



------------------------------------------------------------------------------------------------------------


Step 3:

After notes are added - And while moving to voting.


I see few common themes around external dependencies, time-boxing, access delays, and GitLab updates. Let’s pick the top 2–3 action items we can realistically improve next iteration.”


-------------------------------------------------------------------------------------------------------------------



What went well

  • good progress on policy items
  • documentation improved

  • What could have gone better


    what should we improve in next iteration ; 

    update GitLab comments regularly


    Thanks everyone. Let’s capture 2–3 concrete improvement actions for the next iteration.



    ------------------------------------------------------------------------------------------------------------------

    End : 

    “I’ll capture these improvement points and we’ll track them in the next iteration so they don’t remain only as discussion.”

    OR


    Thanks everyone. I’ll capture these action items and we’ll review them in the next retro to see if we improved.”


    Posted By Nikhil04:34

    Thursday, 4 June 2026

    Filled under:

     You can write it like this:

    Hi Tarun,

    Thanks for the quick catch-up yesterday. I have documented the shared remediation details into steps and started testing them on multiple servers.

    During testing, I noticed one concern after performing the remediation steps. Post-remediation, the DB connection started failing with:

    ORA-28860: Fatal SSL error

    After that, I ran the SHA2 command with the grid option, but the connection then failed with a different error:

    ORA-28043: invalid bind credentials for DB-OID connection

    Later, when I ran the SHA2 command without the grid option, the DB connection started working again.

    At this point, I am not fully sure whether the earlier remediation steps caused the DB connectivity issue, or whether the database already had an existing certificate-related issue that became visible during testing.

    Since this remediation may be applied estate-wide and potentially in production soon, I wanted to highlight this observation and double-confirm the expected behavior before we proceed further.

    Could you please help review this and confirm whether the SHA2 command should be executed with or without the grid option for this use case? Also, is there any additional validation we should perform before considering the remediation safe for estate-wide rollout?

    Regards,

    Nikhil

    Posted By Nikhil08:29
    Filled under:

     Hi [Name], quick reminder on the Red Zone dependency item.


    Since this was carried over and is blocked again due to pending response from Red Zone team, can you please try to arrange a short 15-min catch-up and confirm the owner/next action/ETA before your leave from Monday?


    This will help us avoid carrying the blocker further without clear direction.

    Posted By Nikhil07:02

    Wednesday, 3 June 2026

    Filled under:

     

    Yes Lisa, that’s a valid point. I agree we should not change the common package only for ~30 RAC databases if it creates risk for the wider estate.

    My only concern is that we should also not lose useful RAC metrics from LGTM. Maybe we can keep the existing package unchanged for non-RAC and handle RAC through a specific conditional logic / separate metrics file, so both sides are covered safely.

    Posted By Nikhil08:36
    Filled under:

     

    Thank you for the kind note and recognition.

    I am truly grateful for the support, encouragement, and learning opportunities provided by the organisation and the team. Working in this environment has helped me learn from real enterprise database challenges, collaborate with experienced colleagues, and continuously grow as a professional.

    Being part of the Oracle ACE community allows me to share these learnings and practical experiences with the wider Oracle community outside the organisation. It also helps me stay connected with Oracle product updates, technical overview sessions, community discussions, and opportunities to engage with Oracle product teams.

    I hope this also encourages more team members to stay connected with the Oracle ecosystem, as these learnings and engagements can bring useful value back to our database and engineering work.

    Thank you again for the encouragement and support.

    Posted By Nikhil07:08
    Filled under:

     Impact:

    Some scripts/docs may currently depend on Confluence pages owned by other applications or PODs. If those pages are moved, restricted, renamed, or decommissioned, our documentation or operational references may break.


    Bringing required references into the Emerging DB space will improve ownership, accessibility, consistency, and long-term maintainability.

    Posted By Nikhil05:24
    Filled under:

     

    Hi Tarun,

    Thank you for the detailed inputs.

    I have a few follow-up questions to understand the correct approach before we proceed further across the estate.

    Do we know since when the process moved from STID:WRAPPER / STID:RENEW:WRAPPER to PEM:PISABASEID? Also, do we have the exact documented steps for the PEM:PISABASEID based renewal process? I found something similar here for reference:

    For estate-wide validation, do we have any specific command or known check to confirm whether a host is correctly using PEM:PISABASEID? For STID:WRAPPER, I am currently using the below command/check, but when I try a similar check for PEM:PISABASEID, it does not return anything.

    <add your wrapper command/check here>

    Do we already have any provision or arrangement available to scan the estate for this? If not, could you please advise the exact Tanium command/query we should use to identify hosts with STID:WRAPPER, STID:RENEW:WRAPPER, and PEM:PISABASEID?

    I also have two sample hosts with me for comparison:

    1. Host where PEM:PISABASEID is not listed, but the DB/GI certificates are valid.
    2. Host where STID:WRAPPER is invalid, and the DB/GI certificates are also invalid.

    Could you please help confirm the expected state for such hosts and the correct remediation path?

    Regards,
    Nikhil

    Posted By Nikhil00:46

    Tuesday, 2 June 2026

    Filled under:

     1

    sudo find /etc/pki /usr/share/pki -type f \( -name "*.crt" -o -name "*.pem" -o -name "*.cer" \) 2>/dev/null | grep -i standard

    2.

    openssl x509 -in /path/to/standardID.crt -noout -subject -issuer -serial -fingerprint -sha256 -enddate

    -

    New ##

    1

    echo | openssl s_client -connect server01:443 -servername server01 -showcerts 2>/dev/null

    2 check issuer / subject

    echo | openssl s_client -connect server01:443 -servername server01 -showcerts 2>/dev/null \

    | openssl x509 -noout -subject -issuer -fingerprint -sha256 -enddate

    3.

    servers.txt

    &

    #!/bin/bash

    PORT=443

    HOSTLIST="servers.txt"

    OUTPUT="standardid_port_check_$(date +%F_%H%M).csv"

    echo "HOST,PORT,STATUS,DETAIL" > "$OUTPUT"

    while read -r HOST

    do

    [ -z "$HOST" ] && continue

    echo "Checking $HOST:$PORT ..."

    CERT_INFO=$(timeout 10 bash -c "echo | openssl s_client -connect ${HOST}:${PORT} -servername ${HOST} -showcerts 2>/dev/null \

    | openssl x509 -noout -subject -issuer -fingerprint -sha256 -enddate 2>/dev/null")

    if [ -z "$CERT_INFO" ]; then

    echo "$HOST,$PORT,NO_TLS_OR_CONNECTION_FAILED,\"No certificate returned on this port\"" >> "$OUTPUT"

    continue

    fi

    if echo "$CERT_INFO" | grep -iq "standard"; then

    DETAIL=$(echo "$CERT_INFO" | tr '\n' ' ' | sed 's/"/""/g')

    echo "$HOST,$PORT,FOUND,\"$DETAIL\"" >> "$OUTPUT"

    else

    DETAIL=$(echo "$CERT_INFO" | tr '\n' ' ' | sed 's/"/""/g')

    echo "$HOST,$PORT,NOT_FOUND,\"$DETAIL\"" >> "$OUTPUT"

    fi

    done < "$HOSTLIST"

    echo "Report generated: $OUTPUT"

    #

    openssl x509 -in /etc/pki/ca-trust/source/anchors/standardID.crt -noout -fingerprint -sha256

    sudo find /etc/pki /usr/share/pki -type f \( -name "*.crt" -o -name "*.pem" -o -name "*.cer" \) 2>/dev/null | grep -i standard

    Posted By Nikhil18:10
    Filled under:

     Oracle ACE End-of-Year Highlights 2025 🤞


    Great initiative by the Oracle ACE Program team to share the Oracle ACE End-of-Year Highlights 2025, showcasing the incredible contributions and achievements of ACEs across the globe.

    Happy and honored to see my contributions featured in the highlights and proud to be part of such an amazing global community that continuously shares knowledge and gives back to the Oracle ecosystem.

    A big thank you to the Oracle ACE team for recognizing and celebrating the efforts of ACEs worldwide.

    Chaitanya Koratamaddi | Roopesh Thokala | Oana-Aurelia Bonu | Cassandra Call | Gerald Venzl | India Oracle APEX User Group | All India Oracle Users Group (AIOUG) | Varughese Mathew

    #OracleACE #OracleCommunity #Oracle #OracleAPEX #OracleACEDirector #KnowledgeSharing #CommunityLeadership #TechCommunity #OracleTechnology #2025Highlights #OracleACEProgram #GivingBack #OracleFamily

    Posted By Nikhil07:59