Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
11
Newest
 Tumbleweed
Impact
~6k people reached

  • 0 posts edited
  • 0 helpful flags
  • 16 votes cast
Apr
16
answered Delete Old Archivelogs from missing database
Apr
15
asked Delete Old Archivelogs from missing database
Mar
7
comment sql taking < 1 sec to run in sql developer, 37 on the application side
@thatjeffsmith thank you
Mar
6
comment sql taking < 1 sec to run in sql developer, 37 on the application side
@a1ex07 Ok, thanks for the advices. Out of pressure a coworker decided to rewrite the query differently so unfortunately I cannot test all this anymore. However, I will do it next time we have a similar problem.
Mar
6
comment sql taking < 1 sec to run in sql developer, 37 on the application side
@a1ex07 yeah, must be this...
Mar
6
revised sql taking < 1 sec to run in sql developer, 37 on the application side
edited tags
Mar
5
comment sql taking < 1 sec to run in sql developer, 37 on the application side
@Raj 142 rows returned, it's pretty much instant anyway
Mar
5
comment sql taking < 1 sec to run in sql developer, 37 on the application side
@a1ex07 EXACT
Mar
5
asked sql taking < 1 sec to run in sql developer, 37 on the application side
Jan
27
comment DESCRIPTION_LIST in tnsnames.ora
Thank you for your reply. Yes, what you describe is indeed our scenario. I read about the startup trigger. I will keep it in mind in the future, but so far we found the description_list to be a good and less intrusive alternative. What do you think?
Jan
26
comment DESCRIPTION_LIST in tnsnames.ora
yes exactly. Each rac is a 2 nodes rac.
Jan
26
comment DESCRIPTION_LIST in tnsnames.ora
we use the scan listener for node a to node b in primary rac and in secondary rac with no issue. Failover=on. The problem comes when I have to fail rac1 over rac2: it has to be separate "DESCRIPTION{}" groups because the service names are different.
Jan
23
comment DESCRIPTION_LIST in tnsnames.ora
Our configuration is for failing over a standby database using a different service name, so we cannot use the scan listener. But thanks for the idea though, it made me think of something else
Jan
23
comment DESCRIPTION_LIST in tnsnames.ora
ok, thanks, that's the answer.
Jan
23
revised DESCRIPTION_LIST in tnsnames.ora
edited tags
Jan
23
asked DESCRIPTION_LIST in tnsnames.ora
Nov
28
revised issue granting privileges in a hierarchical user configuration
edited tags
Nov
28
asked issue granting privileges in a hierarchical user configuration
Aug
6
awarded  Tumbleweed
Jul
24
asked How to verify that a certain commit has been transmitted to standby