Slider 1 mini Slider 2 mini

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