Filter API failes to retrieve ARPluginContext

2014-07-09 Thread Jarl Grøneng
Hi



I'm trying to use this method to send alerts to a filter plugin. But it
does not behave as it should:

https://docs.bmc.com/docs/display/public/ars81/Sending+alerts+to+a+filter+API+plug-in



The plugin are not able to fetch context.getUser()) and
context.getUserSessionGuid().



If I use the same plugin as a set field filter plugin I can get those
values, but not when running the plugin as a alert plugin.



Same issue in 7.6.04 p5 and 8.1.01 p1 (win2008)



Regards,

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: HIRING - Remedy Developer Position - Falls Church, VA

2014-07-09 Thread Turner, Jewel (InfoPro-HQ)
Hello ALL:  


 InfoPro is seeking a Remedy Developer to support our government customer in 
Falls Church, VA.  This is a salaried full-time position, it is not open to 
1099 or corp-to-corp.


Talent Service Integrity
  
 
These three words tell you why InfoPro should be your employer of choice.

We believe that our people are the reason for our success, and we back this up 
with a total commitment to the professional and personal success of each and 
every one of our employees, from entry-level personnel to seasoned experts 
across all disciplines and business lines. Our compensation and benefits 
programs are in an elite class in the industry!

The candidate selected for this position will directly support our client’s 
Program Division’s Remedy project.  The project involves analysis, process 
management support, and the development of Remedy solutions using ITSM 6.0 
applications, ARS 7.6, and future migration of Remedy v7.6.04 to the BMC Remedy 
ITSM suite Version 8 or higher.  The ideal candidate demonstrates the ability 
to identify, assess, and articulate various implementation options and 
techniques during project planning, development, and implementation activities. 
 Candidate must demonstrate the ability to recommend, and ultimately implement, 
the successful and cohesive completion of assigned projects. This activity will 
require enough technical and business process exposure to properly articulate 
the appropriate approach, risk and issues on assigned projects.  

Duties and Responsibilities

•   Responsible for successfully developing project customizations and 
support implementations requiring integration with technical teams across 
organizations.
•   Application development, implementation and maintenance 
•   System and infrastructure architecture and design
•   Provide ITIL expertise and guidance to assist in establishing Help 
Desk, Asset Management, Service Request, and Work Order processes.
•   Build test cases, document developer guides, training guides, quick 
reference guides, user guides, support guides etc. 
•   Support Remedy administration and project management tasks as required 
•   Development, analysis, management, and maintenance of functional 
requirements and translation to technical system requirements 
•   Technical writing and documentation management support 

Required Skills

•   Minimum of 9 years general IT experience to include 2 years Remedy 
development experience on versions 7.5 and beyond.
•   Experience with BMC ITSM v7.6.04 components, modules, and related 
skills:
-   Experience with the installation and configuration ARS and ITSM in UNIX 
environment (preferably LINUX) 
-   CMDB 2.1 experience; should be able to create and customize classes as 
well as understand the CDM and its relationships 
-   Configuration and customization of the Asset Management Module
-   Configuration of the Service Request Module (SRM)
-   Configuration of the Work Order Console
-   Configuration and customization of the Service Desk: Incident Module
-   Configuration of the Service Level Management (SLM) module
-   Configuring and defining Foundation Data
-   Development via the BMC Developer Studio and knowledge of overlays
-   WebLogic experience 
-   Comfortable working in an Oracle database; at least 2 years of Oracle 
experience 
-   Familiarity with data loading tools such Atrium Integration Engine and 
Atrium Integrator 
-   Experience with Remedy in both a developer and administrator capacity 
•   ITIL v3 Foundation Certification with 2 years+ experience ITIL and 
process engineering 
•   Knowledge of Active Directory, Authentication
•   Experience configuring server hardware and software
•   Ability to create system requirements and design documents 
•   Must demonstrate experience across all phases of full system 
development life cycle and subsequent maintenance activities
•   Strong commitment to accomplishing the mission
•   Ability to work in a high pressure environment, meet deadlines, and 
simultaneously develop, deploy, and coordinate multiple projects
•   Excellent interpersonal skills and demonstrated ability to work well in 
a team environment, collaborate with various people and organizations in an 
effort to develop win/win results
•   Negotiation skills and the ability to manage expectations
•   Excellent communication skills – both verbal and written
•   Deep level of proficiency and understanding of information technology 
and the linkage between business processes, people and systems
•   Solid business acumen across multiple functional areas/processes 
•   Active participation with the IT and business management teams to 
develop and measure project evaluation criteria and return on investment
• 

Re: custom notification to grp

2014-07-09 Thread Brittain, Mark
If you are only setting up the group for the sake of sending an email 
notification, then I would suggest you have this group set up an email DL, 
which they would maintain. Then create a notify filter which send the email to 
the DL. This way you can set it up and forget it. Otherwise anytime someone 
needs to be added/removed from the notification, you have something to do.

Mark

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W
Sent: Tuesday, July 08, 2014 10:17 AM
To: arslist@ARSLIST.ORG
Subject: Re: custom notification to grp

When you use a Group Name the Email engine should send an email to all members 
of the group

From Developer Studio help  Creating a notify action

AR System group names
AR System takes the group name from the entry in the Group form, searches the 
User form for all users belonging to this group, and delivers the notification 
for each member.
For Alert notifications, an entry is made in the Alert Events form for each 
group member.
Email notifications are sent to the email address specified in the User form 
entry for each user.

Fred

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of S Test
Sent: Tuesday, July 08, 2014 8:57 AM
To: arslist@ARSLIST.ORG
Subject: Re: custom notification to grp

Thanks Todd. That sends a message in AR email message form with field  TO : Grp 
name is placed instead I need email id of all the people in this group

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Arner, Todd
Sent: Tuesday, July 08, 2014 6:16 AM
To: arslist@ARSLIST.ORG
Subject: Re: custom notification to grp

I would use a filter notify action to create the notification.  In the User 
field on the filter notification action enter the group name as it appears in 
the Group form.  This will send the notification to everyone in the group.  
Hope that helps.

Todd Arner

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of S Test
Sent: Monday, July 07, 2014 5:29 PM
To: arslist@ARSLIST.ORG
Subject: custom notification to grp

Hi

I need to design custom notification to all the people in the new grp. The 
ticket won't be assigned to this grp but the grp will be in support grp form. 
What is best way to do this?  Can I use Notify action from filter but how will 
it pull all the individuals in the grp?


Thanks



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers 
Are, and have been for 20 years

This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Slightly OT: Connecting SQL*Plus client to an Oracle Database..

2014-07-09 Thread Joe D'Souza
We have our Remedy database on Oracle 11.2.0.3.0 - 64bit Production server.

 

I am using SQL*Plus Release 10.2.0.1.0 client to connect to it but am unable
to connect with a connection error that reads as:

 

ORA-12154: TNS:could not resolve the connect identifier specified

 

I have checked my tnsnames.ora file for any possible errors in the
connection string and can't seem to find one. This is the contents of the
entry (I  have replaced the actual IP and the service name and what not with
fictitious names for security reasons - the port is 1521 which is the
default port.)

 

## Remedy ITSM db - Devl - Used IP instead of hostname

CONNENTRY =

  (DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

(CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = connentry)

)

  )

 

While connecting I use the username  password as given to me and connentry
as the host string.

 

What could possibly be the causes of ORA-12154 that I ought to check for? I
suspect something wrong with my connection string in my tnsnames.ora file
but can't figure what it is. I checked with the DBA's for the exact IP,
port, service name and they say it all checks out.

 

I was also suspecting that perhaps Oracle client 10.2.0.1.0 may not be
compatible with Oracle Database version 11.2.0.3.0, but I do not think that
could be the problem as Oracle clients are usually compatible with at least
1 version forward or backward.

 

 

Any insights as to what I and my DBA's may be missing may help..

 

Thanks..

 

Joe


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

2014-07-09 Thread Wesley Reyes
Hi Joe,

Kindly do a tnsping of your service_name.  Possible cause is that you cant 
reach your destination host.  Please also try to do a telnet test to the host 
ip with the port 1521 to make sure that the port is open on the fw.

Regards,

Wesley

 On 9 Jul, 2014, at 11:43 pm, Joe D'Souza jdso...@shyle.net wrote:
 
 **
 We have our Remedy database on Oracle 11.2.0.3.0 - 64bit Production server.
  
 I am using SQL*Plus Release 10.2.0.1.0 client to connect to it but am unable 
 to connect with a connection error that reads as:
  
 ORA-12154: TNS:could not resolve the connect identifier specified
  
 I have checked my tnsnames.ora file for any possible errors in the connection 
 string and can’t seem to find one. This is the contents of the entry (I  have 
 replaced the actual IP and the service name and what not with fictitious 
 names for security reasons – the port is 1521 which is the default port.)
  
 ## Remedy ITSM db - Devl - Used IP instead of hostname
 CONNENTRY =
   (DESCRIPTION =
 (ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))
 (CONNECT_DATA =
   (SERVER = DEDICATED)
   (SERVICE_NAME = connentry)
 )
   )
  
 While connecting I use the username  password as given to me and connentry 
 as the host string.
  
 What could possibly be the causes of ORA-12154 that I ought to check for? I 
 suspect something wrong with my connection string in my tnsnames.ora file but 
 can’t figure what it is. I checked with the DBA’s for the exact IP, port, 
 service name and they say it all checks out.
  
 I was also suspecting that perhaps Oracle client 10.2.0.1.0 may not be 
 compatible with Oracle Database version 11.2.0.3.0, but I do not think that 
 could be the problem as Oracle clients are usually compatible with at least 1 
 version forward or backward.
  
  
 Any insights as to what I and my DBA’s may be missing may help..
  
 Thanks..
  
 Joe
 _ARSlist: Where the Answers Are and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Support Groups: Best Practice?

2014-07-09 Thread Timothy Powell
Ok, we had a similar situation with our desktop support people. Here is what
we did.

 

We created separate desktop groups for each location (in your case for each
specific app). So for example: Desktop-Orlando, Desktop-Charlotte, etc. In
your case it might look like Support-App1, Support-App2, etc.

Each of these specific groups only contained the people in that specific
location. In your case, they would only contain the people specifically
responsible for that application.

 

We then created a master group. Call it Desktop-Master. In your case it
might be Application-Master.

We added all members to the Master group.

We added the overall manager to ALL groups as an associate member and marked
them unavailable for assignment. We did this so that the manager could go in
to any group at any time and reassign the ticket from a specific group to
the master group for just the reasons you indicate. In case the specific
group members were unavailable for whatever reason.

 

This reduced the overall number of notifications, gave us some specific data
for reporting and still allowed for maximum coverage as needed.

 

We also built our assignment rules so that the specific groups were
auto-assigned tickets based on location (in your case by specific app) and
made sure they appeared as the first pick in the list if somebody clicked
the Auto-Assign link.

We then configured the assignment rules so that the master group acted as an
auto-assignment catch all group and made sure they appeared 2nd in the
list if somebody clicked the Auto-Assign link, thus establishing a manual
assignment hierarchy.

 

HTH,

Tim

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Champagne, Susan
Sent: Tuesday, July 08, 2014 1:59 PM
To: arslist@ARSLIST.ORG
Subject: Re: Support Groups: Best Practice?

 

** 

Hi Shawn,

Yes, you are correct, each application does have a primary and secondary
support person. The reason I was asked to add all members of the main group
to each individual support group was to ensure coverage in the event that
the 2 actual support people for the application happened to be away at the
same time. This way, another support person would step in and do what they
could with the request. Otherwise, I would be expected to add members to
support groups on-demand, and that would not be reasonable, since I am
alone, supporting Remedy in our organization.

 

Thank you for your input.

 

 

Susan Champagne

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Pierson, Shawn
Sent: July-08-14 1:40 PM
To: arslist@ARSLIST.ORG
Subject: Re: Support Groups: Best Practice?

 

** 

While what you are saying mostly makes sense, 35 groups for 30 people is
very excessive, especially if all 30 people are in all 35 groups with only
one enabled and 29 offline for that group.  It's not practical for 30
people to support 35 applications with everyone covering each other as
backups, purely from a work perspective.

 

My guess is that there is probably a primary and secondary person for each
app, or they are grouped according to purpose, or something.  There has to
be some way to build logical support groups that are smaller.  I'd guess
that you could get them down to 3 - 5 support groups, even though everyone
would need to be added to all of those groups with the tertiary support
staff as offline members of that group.

 

Thanks,

 

Shawn Pierson 

Remedy Developer | Energy Transfer

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Champagne, Susan
Sent: Tuesday, July 08, 2014 12:34 PM
To: arslist@ARSLIST.ORG
Subject: Re: Support Groups: Best Practice?

 

** 

Thank you again Terje.

In answer to your question, yes, every support person, in each of the
support groups, in this discussion, must have the ability to work on any of
the assignments to any of the groups they are members of. 

Our service desk personnel create most tickets and assign to the appropriate
support group, in some cases, or to the appropriate individual in other
cases. We do not have any assignment automation configured at this time.

 

Thank you again Terje; your input is much appreciated.

 

 

Susan Champagne

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Terje Moglestue
Sent: July-08-14 1:14 PM
To: arslist@ARSLIST.ORG
Subject: Re: Support Groups: Best Practice?

 

** 

Susan,

 

I find it difficult to understand why you want all support user should be
member of all teams. If the support staff got unlimited access - they can
still search all tickets. A support engineer can only modify tickets
assigned to a group where he is a member. Is this the reason why you want
all support members to member of all groups? Are every support engineer
working and updating the tickets across all the support groups?

 

A support group performance is normally done based on all the 

Re: Support Groups: Best Practice?

2014-07-09 Thread Timothy Powell
Oh.and this greatly reduced our data management workload. If something
changed in ref to people and the group he/she is in, all I now have to do is
management membership for the specific local group and the master group (vs.
having to adjust 35 groups in your potential situation).

 

Tim 

 

From: Timothy Powell [mailto:timothy.pow...@pbs-consulting.com] 
Sent: Wednesday, July 09, 2014 12:02 PM
To: 'arslist@ARSLIST.ORG'
Subject: RE: Support Groups: Best Practice?

 

Ok, we had a similar situation with our desktop support people. Here is what
we did.

 

We created separate desktop groups for each location (in your case for each
specific app). So for example: Desktop-Orlando, Desktop-Charlotte, etc. In
your case it might look like Support-App1, Support-App2, etc.

Each of these specific groups only contained the people in that specific
location. In your case, they would only contain the people specifically
responsible for that application.

 

We then created a master group. Call it Desktop-Master. In your case it
might be Application-Master.

We added all members to the Master group.

We added the overall manager to ALL groups as an associate member and marked
them unavailable for assignment. We did this so that the manager could go in
to any group at any time and reassign the ticket from a specific group to
the master group for just the reasons you indicate. In case the specific
group members were unavailable for whatever reason.

 

This reduced the overall number of notifications, gave us some specific data
for reporting and still allowed for maximum coverage as needed.

 

We also built our assignment rules so that the specific groups were
auto-assigned tickets based on location (in your case by specific app) and
made sure they appeared as the first pick in the list if somebody clicked
the Auto-Assign link.

We then configured the assignment rules so that the master group acted as an
auto-assignment catch all group and made sure they appeared 2nd in the
list if somebody clicked the Auto-Assign link, thus establishing a manual
assignment hierarchy.

 

HTH,

Tim

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Champagne, Susan
Sent: Tuesday, July 08, 2014 5:24 PM
To: arslist@ARSLIST.ORG
Subject: Re: Support Groups: Best Practice?

 

** 

Hi Tim,

The end goal, from the requester's view, is to eliminate the currently set
process of Assignment to Individuals. I am in total agreement of getting
to this end result; it's just that I feel we could/should accomplish this
end result in a different manner. The manager of the group wants to have the
ability for his users to be able to filter the Overview Console, to show
only incidents assigned to the groups they select. As I mentioned earlier,
each individual (30 people) will be in each support group (35 groups). I
really hoped I could convince them to use the Product Name as a sorting
option in the Overview Console, instead. The reporting could also be done on
the Product Name.

 

Susan Champagne

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Timothy Powell
Sent: July-08-14 12:06 PM
To: arslist@ARSLIST.ORG
Subject: Re: Support Groups: Best Practice?

 

** 

What is the end goal of this request? WHY are they wanting 35 groups?
Knowing the desired result might help guide some of our thoughts and
responses.

 

Tim

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Champagne, Susan
Sent: Tuesday, July 08, 2014 10:19 AM
To: arslist@ARSLIST.ORG
Subject: Support Groups: Best Practice?

 

** 

Hi folks,

I'm looking to get some advice on what the best practice is regarding Remedy
support groups. I have a group of 30 support staff members, who support many
different applications, and many individual modules in some applications.
They are asking that I create individual support groups for each area of
support. This would be 35 support groups. Originally, when we built the
system in 2009 (7.0.03), we had one support group for these people, but we
used the Assign to Individual practice, which is becoming increasingly
more difficult as the group grows and as their support model grows. We are
now at 7.6.04.

I am looking at suggesting that we leave them in one support group, and I
would add the Product Name field to the assignment notification message,
allowing them to determine if the assignment is for them or not. My dilemma
is on how to convince them that this would be the best way to proceed. 

Your input on this matter would be most appreciated. 

Thank you,

Susan Champagne

 



The information contained in this e-mail and document(s) attached are for
the exclusive use of the addressee and may contain confidential, privileged
and non-disclosable information. If the recipient of this e-mail is not the
addressee, such recipient is strictly prohibited 

Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

2014-07-09 Thread Andrew Hicox
Can anyone else connect to the DB without being on localhost with it?

If no other remote client can connect, maybe the listener isn't running?
Also if others can connect, try copying their tnsnames.ora file

Andy

On Wednesday, July 9, 2014, Joe D'Souza jdso...@shyle.net wrote:

 **

 We have our Remedy database on Oracle 11.2.0.3.0 - 64bit Production server.



 I am using SQL*Plus Release 10.2.0.1.0 client to connect to it but am
 unable to connect with a connection error that reads as:



 ORA-12154: TNS:could not resolve the connect identifier specified



 I have checked my tnsnames.ora file for any possible errors in the
 connection string and can’t seem to find one. This is the contents of the
 entry (I  have replaced the actual IP and the service name and what not
 with fictitious names for security reasons – the port is 1521 which is the
 default port.)



 ## Remedy ITSM db - Devl - Used IP instead of hostname

 CONNENTRY =

   (DESCRIPTION =

 (ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

 (CONNECT_DATA =

   (SERVER = DEDICATED)

   (SERVICE_NAME = connentry)

 )

   )



 While connecting I use the username  password as given to me and
 connentry as the host string.



 What could possibly be the causes of ORA-12154 that I ought to check for?
 I suspect something wrong with my connection string in my tnsnames.ora file
 but can’t figure what it is. I checked with the DBA’s for the exact IP,
 port, service name and they say it all checks out.



 I was also suspecting that perhaps Oracle client 10.2.0.1.0 may not be
 compatible with Oracle Database version 11.2.0.3.0, but I do not think that
 could be the problem as Oracle clients are usually compatible with at least
 1 version forward or backward.





 Any insights as to what I and my DBA’s may be missing may help..



 Thanks..



 Joe
  _ARSlist: Where the Answers Are and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Support Groups: Best Practice?

2014-07-09 Thread Champagne, Susan


Hi Tim,
Thanks so much for sharing your organization's Support Group structure. It 
sounds like a good way to go, however, I believe I have come to a conclusion 
with my dilemma. I have found that I can give limited access to the support 
groups' team leads to be able to add and remove members on their own.
So, with this access:

* There is no concern about me being available to add or remove support 
group members on the fly

* The incidents will remain assigned to the appropriate support group, 
which is part of the reporting requirements.

* The support groups will only consist of the primary and secondary 
support persons, plus the team leads

* The number of notification messages will decrease substantially.

I have learned a lot from the information you and others have shared with me. I 
truly appreciate it.

Thanks again,
Susan Champagne

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Timothy Powell
Sent: July-09-14 12:05 PM
To: arslist@ARSLIST.ORG
Subject: Re: Support Groups: Best Practice?

**
Oh...and this greatly reduced our data management workload. If something 
changed in ref to people and the group he/she is in, all I now have to do is 
management membership for the specific local group and the master group (vs. 
having to adjust 35 groups in your potential situation).

Tim

From: Timothy Powell [mailto:timothy.pow...@pbs-consulting.com]
Sent: Wednesday, July 09, 2014 12:02 PM
To: 'arslist@ARSLIST.ORG'
Subject: RE: Support Groups: Best Practice?

Ok, we had a similar situation with our desktop support people. Here is what we 
did.

We created separate desktop groups for each location (in your case for each 
specific app). So for example: Desktop-Orlando, Desktop-Charlotte, etc. In your 
case it might look like Support-App1, Support-App2, etc.
Each of these specific groups only contained the people in that specific 
location. In your case, they would only contain the people specifically 
responsible for that application.

We then created a master group. Call it Desktop-Master. In your case it might 
be Application-Master.
We added all members to the Master group.
We added the overall manager to ALL groups as an associate member and marked 
them unavailable for assignment. We did this so that the manager could go in to 
any group at any time and reassign the ticket from a specific group to the 
master group for just the reasons you indicate. In case the specific group 
members were unavailable for whatever reason.

This reduced the overall number of notifications, gave us some specific data 
for reporting and still allowed for maximum coverage as needed.

We also built our assignment rules so that the specific groups were 
auto-assigned tickets based on location (in your case by specific app) and made 
sure they appeared as the first pick in the list if somebody clicked the 
Auto-Assign link.
We then configured the assignment rules so that the master group acted as an 
auto-assignment catch all group and made sure they appeared 2nd in the list 
if somebody clicked the Auto-Assign link, thus establishing a manual assignment 
hierarchy.

HTH,
Tim

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Champagne, Susan
Sent: Tuesday, July 08, 2014 5:24 PM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Re: Support Groups: Best Practice?

**
Hi Tim,
The end goal, from the requester's view, is to eliminate the currently set 
process of Assignment to Individuals. I am in total agreement of getting to 
this end result; it's just that I feel we could/should accomplish this end 
result in a different manner. The manager of the group wants to have the 
ability for his users to be able to filter the Overview Console, to show only 
incidents assigned to the groups they select. As I mentioned earlier, each 
individual (30 people) will be in each support group (35 groups). I really 
hoped I could convince them to use the Product Name as a sorting option in the 
Overview Console, instead. The reporting could also be done on the Product Name.

Susan Champagne

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Timothy Powell
Sent: July-08-14 12:06 PM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Re: Support Groups: Best Practice?

**
What is the end goal of this request? WHY are they wanting 35 groups? Knowing 
the desired result might help guide some of our thoughts and responses.

Tim

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Champagne, Susan
Sent: Tuesday, July 08, 2014 10:19 AM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Support Groups: Best Practice?

**

Hi folks,

I'm looking to get some advice on what the best practice is regarding Remedy 
support groups. I have a group of 30 support staff members, who support many 
different applications, 

Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

2014-07-09 Thread Joe D'Souza
The only other person I know who actively connects to the database using a
Oracle client uses the Squirrel client to connect  having not ever used
that client before didn't want to 'try something new'. I did take the
connection string they use there and translated it to the format that
SQL*Plus requires so I'm pretty sure there should not be any problem with
that.

 

Thanks for your response.

 

Joe

 

  _  

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Andrew Hicox
Sent: Wednesday, July 09, 2014 12:20 PM
To: arslist@ARSLIST.ORG
Subject: Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

 

** Can anyone else connect to the DB without being on localhost with it?

 

If no other remote client can connect, maybe the listener isn't running?
Also if others can connect, try copying their tnsnames.ora file

 

Andy

On Wednesday, July 9, 2014, Joe D'Souza jdso...@shyle.net wrote:

** 

We have our Remedy database on Oracle 11.2.0.3.0 - 64bit Production server.

 

I am using SQL*Plus Release 10.2.0.1.0 client to connect to it but am unable
to connect with a connection error that reads as:

 

ORA-12154: TNS:could not resolve the connect identifier specified

 

I have checked my tnsnames.ora file for any possible errors in the
connection string and can't seem to find one. This is the contents of the
entry (I  have replaced the actual IP and the service name and what not with
fictitious names for security reasons - the port is 1521 which is the
default port.)

 

## Remedy ITSM db - Devl - Used IP instead of hostname

CONNENTRY =

  (DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

(CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = connentry)

)

  )

 

While connecting I use the username  password as given to me and connentry
as the host string.

 

What could possibly be the causes of ORA-12154 that I ought to check for? I
suspect something wrong with my connection string in my tnsnames.ora file
but can't figure what it is. I checked with the DBA's for the exact IP,
port, service name and they say it all checks out.

 

I was also suspecting that perhaps Oracle client 10.2.0.1.0 may not be
compatible with Oracle Database version 11.2.0.3.0, but I do not think that
could be the problem as Oracle clients are usually compatible with at least
1 version forward or backward.

 

 

Any insights as to what I and my DBA's may be missing may help..

 

Thanks..

 

Joe

_ARSlist: Where the Answers Are and have been for 20 years_ 

_ARSlist: Where the Answers Are and have been for 20 years_ 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

2014-07-09 Thread Joe D'Souza
I can connect to other databases whose connection strings are defined in
that tnsnames.ora file. So that rules out the client not being able to find
the tnsnames.ora file or any permission related issue to that file.

 

I haven't made any changes to the sqlnet.ora file. The only two non
commented lines in it are:

 

SQLNET.AUTHENTICATION_SERVICES= (NTS)

 

NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

 

Cheers

 

 

 

  _  

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W
Sent: Wednesday, July 09, 2014 12:20 PM
To: arslist@ARSLIST.ORG
Subject: Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

 

I can think of 2 possible reasons off the top of my head.

 

One reason is that SQLPLUS could not find the TNSNAMES.ORA file.   Do you
have an environment variable of TNS_ADMIN?

In my systems I have that environment variable pointing to the folder where
the tnsnames.ora file is located.  SQLPLUS (and the Oracle client in
general) use this environment variable to find the tnsnames.ora
configuration file.

 

Another possible reason could be a default domain setting.

In your Oracle Client configuration do you have an SQLNET.ORA configuration
file that defines?

names.default_domain = world

 

In those cases the TNSNAMES entry wanted to be:   

CONNENTRY.WORLD =

  (DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

(CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = connentry)

)

  )

 

And then my login using SQLPLUS would be

sqlplus user@CONNENTRY.WORLD

 

Fred

 

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Joe D'Souza
Sent: Wednesday, July 09, 2014 10:44 AM
To: arslist@ARSLIST.ORG
Subject: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

 

** 

We have our Remedy database on Oracle 11.2.0.3.0 - 64bit Production server.

 

I am using SQL*Plus Release 10.2.0.1.0 client to connect to it but am unable
to connect with a connection error that reads as:

 

ORA-12154: TNS:could not resolve the connect identifier specified

 

I have checked my tnsnames.ora file for any possible errors in the
connection string and can't seem to find one. This is the contents of the
entry (I  have replaced the actual IP and the service name and what not with
fictitious names for security reasons - the port is 1521 which is the
default port.)

 

## Remedy ITSM db - Devl - Used IP instead of hostname

CONNENTRY =

  (DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

(CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = connentry)

)

  )

 

While connecting I use the username  password as given to me and connentry
as the host string.

 

What could possibly be the causes of ORA-12154 that I ought to check for? I
suspect something wrong with my connection string in my tnsnames.ora file
but can't figure what it is. I checked with the DBA's for the exact IP,
port, service name and they say it all checks out.

 

I was also suspecting that perhaps Oracle client 10.2.0.1.0 may not be
compatible with Oracle Database version 11.2.0.3.0, but I do not think that
could be the problem as Oracle clients are usually compatible with at least
1 version forward or backward.

 

 

Any insights as to what I and my DBA's may be missing may help..

 

Thanks..

 

Joe

 

 

_ARSlist: Where the Answers Are and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

2014-07-09 Thread patrick zandi
you need to set your ORACLE_HOME variable / your ORACLE_SID and your
ORACLE_UNIQUE variable.
then the application should work.



On Wed, Jul 9, 2014 at 4:25 PM, Joe D'Souza jdso...@shyle.net wrote:

 **

 I can connect to other databases whose connection strings are defined in
 that tnsnames.ora file. So that rules out the client not being able to find
 the tnsnames.ora file or any permission related issue to that file.



 I haven’t made any changes to the sqlnet.ora file. The only two non
 commented lines in it are:



 SQLNET.AUTHENTICATION_SERVICES= (NTS)



 NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)



 Cheers






  --

 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Grooms, Frederick W

 *Sent:* Wednesday, July 09, 2014 12:20 PM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Re: Slightly OT: Connecting SQL*Plus client to an Oracle
 Database..



 I can think of 2 possible reasons off the top of my head.



 One reason is that SQLPLUS could not find the TNSNAMES.ORA file.   Do you
 have an environment variable of TNS_ADMIN?

 In my systems I have that environment variable pointing to the folder
 where the tnsnames.ora file is located.  SQLPLUS (and the Oracle client in
 general) use this environment variable to find the tnsnames.ora
 configuration file.



 Another possible reason could be a default domain setting.

 In your Oracle Client configuration do you have an SQLNET.ORA
 configuration file that defines?

 names.default_domain = world



 In those cases the TNSNAMES entry wanted to be:

 CONNENTRY.WORLD =

   (DESCRIPTION =

 (ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

 (CONNECT_DATA =

   (SERVER = DEDICATED)

   (SERVICE_NAME = connentry)

 )

   )



 And then my login using SQLPLUS would be

 sqlplus user@CONNENTRY.WORLD



 Fred





 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Joe D'Souza
 *Sent:* Wednesday, July 09, 2014 10:44 AM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Slightly OT: Connecting SQL*Plus client to an Oracle Database..



 **

 We have our Remedy database on Oracle 11.2.0.3.0 - 64bit Production server.



 I am using SQL*Plus Release 10.2.0.1.0 client to connect to it but am
 unable to connect with a connection error that reads as:



 ORA-12154: TNS:could not resolve the connect identifier specified



 I have checked my tnsnames.ora file for any possible errors in the
 connection string and can’t seem to find one. This is the contents of the
 entry (I  have replaced the actual IP and the service name and what not
 with fictitious names for security reasons – the port is 1521 which is the
 default port.)



 ## Remedy ITSM db - Devl - Used IP instead of hostname

 CONNENTRY =

   (DESCRIPTION =

 (ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

 (CONNECT_DATA =

   (SERVER = DEDICATED)

   (SERVICE_NAME = connentry)

 )

   )



 While connecting I use the username  password as given to me and
 connentry as the host string.



 What could possibly be the causes of ORA-12154 that I ought to check for?
 I suspect something wrong with my connection string in my tnsnames.ora file
 but can’t figure what it is. I checked with the DBA’s for the exact IP,
 port, service name and they say it all checks out.



 I was also suspecting that perhaps Oracle client 10.2.0.1.0 may not be
 compatible with Oracle Database version 11.2.0.3.0, but I do not think that
 could be the problem as Oracle clients are usually compatible with at least
 1 version forward or backward.





 Any insights as to what I and my DBA’s may be missing may help..



 Thanks..



 Joe




  _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist:
 Where the Answers Are and have been for 20 years_




-- 
Patrick Zandi

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

2014-07-09 Thread patrick zandi
Sorry got interupted,  then ensure your /etc/hosts file has the ip address
do a tnsping first
using the oracle tnsnames.ora



On Wed, Jul 9, 2014 at 4:41 PM, patrick zandi remedy...@gmail.com wrote:

 you need to set your ORACLE_HOME variable / your ORACLE_SID and your
 ORACLE_UNIQUE variable.
 then the application should work.



 On Wed, Jul 9, 2014 at 4:25 PM, Joe D'Souza jdso...@shyle.net wrote:

 **

 I can connect to other databases whose connection strings are defined in
 that tnsnames.ora file. So that rules out the client not being able to find
 the tnsnames.ora file or any permission related issue to that file.



 I haven’t made any changes to the sqlnet.ora file. The only two non
 commented lines in it are:



 SQLNET.AUTHENTICATION_SERVICES= (NTS)



 NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)



 Cheers






  --

 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Grooms, Frederick W

 *Sent:* Wednesday, July 09, 2014 12:20 PM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Re: Slightly OT: Connecting SQL*Plus client to an Oracle
 Database..



 I can think of 2 possible reasons off the top of my head.



 One reason is that SQLPLUS could not find the TNSNAMES.ORA file.   Do you
 have an environment variable of TNS_ADMIN?

 In my systems I have that environment variable pointing to the folder
 where the tnsnames.ora file is located.  SQLPLUS (and the Oracle client in
 general) use this environment variable to find the tnsnames.ora
 configuration file.



 Another possible reason could be a default domain setting.

 In your Oracle Client configuration do you have an SQLNET.ORA
 configuration file that defines?

 names.default_domain = world



 In those cases the TNSNAMES entry wanted to be:

 CONNENTRY.WORLD =

   (DESCRIPTION =

 (ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

 (CONNECT_DATA =

   (SERVER = DEDICATED)

   (SERVICE_NAME = connentry)

 )

   )



 And then my login using SQLPLUS would be

 sqlplus user@CONNENTRY.WORLD



 Fred





 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Joe D'Souza
 *Sent:* Wednesday, July 09, 2014 10:44 AM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Slightly OT: Connecting SQL*Plus client to an Oracle
 Database..



 **

 We have our Remedy database on Oracle 11.2.0.3.0 - 64bit Production
 server.



 I am using SQL*Plus Release 10.2.0.1.0 client to connect to it but am
 unable to connect with a connection error that reads as:



 ORA-12154: TNS:could not resolve the connect identifier specified



 I have checked my tnsnames.ora file for any possible errors in the
 connection string and can’t seem to find one. This is the contents of the
 entry (I  have replaced the actual IP and the service name and what not
 with fictitious names for security reasons – the port is 1521 which is the
 default port.)



 ## Remedy ITSM db - Devl - Used IP instead of hostname

 CONNENTRY =

   (DESCRIPTION =

 (ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

 (CONNECT_DATA =

   (SERVER = DEDICATED)

   (SERVICE_NAME = connentry)

 )

   )



 While connecting I use the username  password as given to me and
 connentry as the host string.



 What could possibly be the causes of ORA-12154 that I ought to check for?
 I suspect something wrong with my connection string in my tnsnames.ora file
 but can’t figure what it is. I checked with the DBA’s for the exact IP,
 port, service name and they say it all checks out.



 I was also suspecting that perhaps Oracle client 10.2.0.1.0 may not be
 compatible with Oracle Database version 11.2.0.3.0, but I do not think that
 could be the problem as Oracle clients are usually compatible with at least
 1 version forward or backward.





 Any insights as to what I and my DBA’s may be missing may help..



 Thanks..



 Joe




  _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist:
 Where the Answers Are and have been for 20 years_




 --
 Patrick Zandi




-- 
Patrick Zandi

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

2014-07-09 Thread patrick zandi
IF you are using the ORACE_RAC we have found some additional settings in
the TNSNAMES.ora need to be applied AND you have some additional settings
you have to modify in the SLM module, due to the fact that remedy wrote the
code to do it static like  name:sid:table  or something like that...

hope that helps some.


On Wed, Jul 9, 2014 at 4:42 PM, patrick zandi remedy...@gmail.com wrote:

 Sorry got interupted,  then ensure your /etc/hosts file has the ip address
 do a tnsping first
 using the oracle tnsnames.ora



 On Wed, Jul 9, 2014 at 4:41 PM, patrick zandi remedy...@gmail.com wrote:

 you need to set your ORACLE_HOME variable / your ORACLE_SID and your
 ORACLE_UNIQUE variable.
 then the application should work.



  On Wed, Jul 9, 2014 at 4:25 PM, Joe D'Souza jdso...@shyle.net wrote:

 **

 I can connect to other databases whose connection strings are defined in
 that tnsnames.ora file. So that rules out the client not being able to find
 the tnsnames.ora file or any permission related issue to that file.



 I haven’t made any changes to the sqlnet.ora file. The only two non
 commented lines in it are:



 SQLNET.AUTHENTICATION_SERVICES= (NTS)



 NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)



 Cheers






  --

 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Grooms, Frederick W

 *Sent:* Wednesday, July 09, 2014 12:20 PM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Re: Slightly OT: Connecting SQL*Plus client to an Oracle
 Database..



 I can think of 2 possible reasons off the top of my head.



 One reason is that SQLPLUS could not find the TNSNAMES.ORA file.   Do
 you have an environment variable of TNS_ADMIN?

 In my systems I have that environment variable pointing to the folder
 where the tnsnames.ora file is located.  SQLPLUS (and the Oracle client in
 general) use this environment variable to find the tnsnames.ora
 configuration file.



 Another possible reason could be a default domain setting.

 In your Oracle Client configuration do you have an SQLNET.ORA
 configuration file that defines?

 names.default_domain = world



 In those cases the TNSNAMES entry wanted to be:

 CONNENTRY.WORLD =

   (DESCRIPTION =

 (ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

 (CONNECT_DATA =

   (SERVER = DEDICATED)

   (SERVICE_NAME = connentry)

 )

   )



 And then my login using SQLPLUS would be

 sqlplus user@CONNENTRY.WORLD



 Fred





 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Joe D'Souza
 *Sent:* Wednesday, July 09, 2014 10:44 AM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Slightly OT: Connecting SQL*Plus client to an Oracle
 Database..



 **

 We have our Remedy database on Oracle 11.2.0.3.0 - 64bit Production
 server.



 I am using SQL*Plus Release 10.2.0.1.0 client to connect to it but am
 unable to connect with a connection error that reads as:



 ORA-12154: TNS:could not resolve the connect identifier specified



 I have checked my tnsnames.ora file for any possible errors in the
 connection string and can’t seem to find one. This is the contents of the
 entry (I  have replaced the actual IP and the service name and what not
 with fictitious names for security reasons – the port is 1521 which is the
 default port.)



 ## Remedy ITSM db - Devl - Used IP instead of hostname

 CONNENTRY =

   (DESCRIPTION =

 (ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))

 (CONNECT_DATA =

   (SERVER = DEDICATED)

   (SERVICE_NAME = connentry)

 )

   )



 While connecting I use the username  password as given to me and
 connentry as the host string.



 What could possibly be the causes of ORA-12154 that I ought to check
 for? I suspect something wrong with my connection string in my tnsnames.ora
 file but can’t figure what it is. I checked with the DBA’s for the exact
 IP, port, service name and they say it all checks out.



 I was also suspecting that perhaps Oracle client 10.2.0.1.0 may not be
 compatible with Oracle Database version 11.2.0.3.0, but I do not think that
 could be the problem as Oracle clients are usually compatible with at least
 1 version forward or backward.





 Any insights as to what I and my DBA’s may be missing may help..



 Thanks..



 Joe




  _ARSlist: Where the Answers Are and have been for 20 years_
 _ARSlist: Where the Answers Are and have been for 20 years_




 --
 Patrick Zandi




 --
 Patrick Zandi




-- 
Patrick Zandi

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

2014-07-09 Thread William Rentfrow
I've seen two different times where the tnsnames.ora file had some type of 
invisible control character in it and the file would not work.

We'd re-type it and try again and it worked - even though the files would be 
identical to visual inspection and were checked by multiple people.

If you're on Unix you might want to run dos2unix on the file.

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W
Sent: Wednesday, July 09, 2014 3:51 PM
To: arslist@ARSLIST.ORG
Subject: Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

**
Ok ... Since you can connect to other databases listed in the TNSNAMES.ORA file 
that should rule that out


Since you have SQLNET.AUTHENTICATION_SERVICES= (NTS) I wonder if there is a 
permissions issue with the user and password you were given.



NTS uses Windows native authentication to allow access to a database.  If you 
are specifying a user and password yourself I usually prefer to set this to 
NONE or comment out that line in the sqlnet.ora file.



Fred

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Joe D'Souza
Sent: Wednesday, July 09, 2014 3:25 PM
To: arslist@ARSLIST.ORG
Subject: Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

**
I can connect to other databases whose connection strings are defined in that 
tnsnames.ora file. So that rules out the client not being able to find the 
tnsnames.ora file or any permission related issue to that file.


I haven't made any changes to the sqlnet.ora file. The only two non commented 
lines in it are:



SQLNET.AUTHENTICATION_SERVICES= (NTS)



NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)



Cheers






From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W
Sent: Wednesday, July 09, 2014 12:20 PM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Re: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

I can think of 2 possible reasons off the top of my head.

One reason is that SQLPLUS could not find the TNSNAMES.ORA file.   Do you have 
an environment variable of TNS_ADMIN?
In my systems I have that environment variable pointing to the folder where the 
tnsnames.ora file is located.  SQLPLUS (and the Oracle client in general) use 
this environment variable to find the tnsnames.ora configuration file.

Another possible reason could be a default domain setting.
In your Oracle Client configuration do you have an SQLNET.ORA configuration 
file that defines?
names.default_domain = world

In those cases the TNSNAMES entry wanted to be:
CONNENTRY.WORLD =
  (DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))
(CONNECT_DATA =
  (SERVER = DEDICATED)
  (SERVICE_NAME = connentry)
)
  )

And then my login using SQLPLUS would be
sqlplus user@CONNENTRY.WORLDmailto:user@CONNENTRY.WORLD

Fred


From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Joe D'Souza
Sent: Wednesday, July 09, 2014 10:44 AM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Slightly OT: Connecting SQL*Plus client to an Oracle Database..

**
We have our Remedy database on Oracle 11.2.0.3.0 - 64bit Production server.

I am using SQL*Plus Release 10.2.0.1.0 client to connect to it but am unable to 
connect with a connection error that reads as:

ORA-12154: TNS:could not resolve the connect identifier specified

I have checked my tnsnames.ora file for any possible errors in the connection 
string and can't seem to find one. This is the contents of the entry (I  have 
replaced the actual IP and the service name and what not with fictitious names 
for security reasons - the port is 1521 which is the default port.)

## Remedy ITSM db - Devl - Used IP instead of hostname
CONNENTRY =
  (DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 111.111.11.111)(PORT = 1521))
(CONNECT_DATA =
  (SERVER = DEDICATED)
  (SERVICE_NAME = connentry)
)
  )

While connecting I use the username  password as given to me and connentry as 
the host string.

What could possibly be the causes of ORA-12154 that I ought to check for? I 
suspect something wrong with my connection string in my tnsnames.ora file but 
can't figure what it is. I checked with the DBA's for the exact IP, port, 
service name and they say it all checks out.

I was also suspecting that perhaps Oracle client 10.2.0.1.0 may not be 
compatible with Oracle Database version 11.2.0.3.0, but I do not think that 
could be the problem as Oracle clients are usually compatible with at least 1 
version forward or backward.


Any insights as to what I and my DBA's may be missing may help..

Thanks..


Joe





No virus found in this message.
Checked by AVG - www.avg.comhttp://www.avg.com
Version: 2014.0.4716 / Virus Database: 3986/7812 - Release