Siebel CRM – Version 8.1.1 SIA [21111] and later
Information in this document applies to any platform.
***Checked for relevance on 07-Feb-2013***


We cannot duplicate any object from the view “Enterprise Component Definition View (Configuration)”. Every time we try to do it, we get the message we attach in this SR.

The following errors can be seen in the object manager logs:

GenericLog GenericError 1 0000002d4ba82134:0 2010-03-23 10:46:09 (srsqobj.cpp (448) err=3015682 sys=0) SBL-CSO-01026: Interno: la operación de consulta no es válida para el almacenamiento de datos y el tipo de objeto especificados.

SisnTcpIp SisnSockDetail 4 0000002d4ba82134:0 2010-03-23 10:46:09  8856: [TCPIP-client] Send() descriptor = 2632

GenericLog GenericError 1 00004f384ba0256c:0 2010-03-23 10:46:09 (saconn.cpp (234) err=590873 sys=0) SBL-ADM-01049: Ha intentado definir un componente con el mismo alias que una definición de componente existente. Dé al componente un alias que sea único.

GenericLog GenericError 1 00004f384ba0256c:0 2010-03-23 10:46:09 (sacmd.cpp (552) err=649894 sys=0) SBL-ADM-60070: Se ha informado del siguiente error en el servidor ‘Gateway Server’:


The following configuration change needs to be implemented to resolve this issue.

Modify the business component “Enterprise Service Definitions”

Step 1 : Open Siebel tools . Go to the View “Business Component”  Click on Query
Step 2 : Query for “Enterprise Service Definitions” in the name column
Step 3 : Go to the fields section under the business component “Enterprise Service Definitions”
Step 4 : Query for the field “Multi-threaded” in the name column
Step 5 : For the field “Multi-threaded” , select “No Copy” to true
Step 6 : Please compile the changes to the SRF and restart the siebel servers with the compiled SRF .


Posted: June 17, 2015 in Siebel
Tags: , ,

I think is a necessary information before we go for DeDuplicfation configuration, so copied from the

Using Deduplication is a relatively big architectural decision.
You would need to think about the following amongst various others.

1. Are you licenced to use Siebel Data Quality ?
2. If you are licenced already, you need to check if your license us for SSA or Firstlogic or some other Matching vendor. The user properties at the BC are different for each vendor.
2. You need to setup DQ connectors and configure the OM component to use DQ matching.
3. The default object manager real time matching does not error out when it finds duplicates. It provides the user with a list of Matching records with a percentage against them. The user can decide to select one of them or proceed with creating a new record. If you want to error out, you still need to write script to call the “DeDuplication” business service Match method.

Before you go down the deduplication path, I have the following thoughts about your requirement.
The ideal way to implement this requirement would be to add a unique index on the Table object(including the 4 colums and the Conflict Id column). However, I understand you dont want to do that. Is that because the table is shared by many BCs and you want to apply this validation to just 1 BC ?
If you write any validation on the BC and if your application has remote users or has replicated environments, you validation is going to be of no use as its only going to check for the local duplicate records. It will fail during synchronization because there is no User key or Unique index(with Conflict Id) and the system will blindly allow new duplicates to be synched.

Even if you dont care about remote or replication, you need to think about performance implications. If the BC concerned is a relatively large volume BC, it is a considerable overhead to do a Query on the same BC(instanciating a standalone BO) on every writerecord. You need to think about at least adding a non-unique index or consult with your DBA if you need one.

To summarise, I’d only go ahead with this requirement if you don’t have remote/replication and the BC is a low volume BC. I would always go back to business and explain the consequences before I implement anything non-standard.

Hope it helps.

Posted: April 23, 2015 in Siebel

How To Analyze the FDR Output in Siebel Versions 7.7.x, 7.8.x and 8. (Doc ID 473939.1)

Applies to:

Siebel CRM – Version 7.7.1 [18306] to 8.1.1 [21112] [Release V7 to V8]
Information in this document applies to any platform.
Area(s):System Administration
Release(s):V7 (Enterprise), V7 (Professional)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)

This document was previously published as Siebel Technical Note 650.

Checked for relevance 08 Jan 2014


FDR stands for Flight Data Recorder and is a framework in the Siebel Server infrastructure that collects data about the running Siebel application in a circular buffer. In the event of a crash, the data is written in binary format to a file in the application /bin subdirectory. The file that is written has the .fdr extension and can be post-processed into human readable format using the sarmanalyzer.exe utility. The data in the output can help show what was happening immediately prior to the crash in different application subsystems.
NOTE: The application may not generate an FDR file when there is a “soft” crash meaning that the server process exits but is not recognized by the Siebel crash handler. This can happen when one of the following occurs:
  • The Siebel crash handler is disabled (should only happen under the supervision of Technical Support).
  • When the process exits, it does not go through the internal code path that executes the Siebel crash handler logic and none of the related crash output for example the crash.txt file or FDR file is created.


This document is informational and intended for any user.


Here are the high level sections that are covered in this document. Click on any of the items below to jumplink to that section:
  • How to Identify the Correct FDR file When a Crash Occurs
  • How to Process Binary .fdr File into .csv Format and Identify the Crashing Thread
  • How to Flush FDR Output
  • How to Review Entries Prior to Crashing Thread to Understand What Happened Immediately Prior to the Crash
    • Example Case
    • Diagram of Interaction between Elements Involved in Crash Scenario
    • Analysis of the FDR output:
  • Where to go for more information

How to Identify the Correct FDR file When a Crash Occurs

Finding the correct output file can be done by using the information in the .fdr file name. The file name includes a timestamp and the process id that crashed and is written in the format:
T<YYYYMMDDHHMM>_P<process id value>.fdr
For example:
Is a file name that is based on a component that was started on March 18, 2005 at 4:01 PM where the process id value was 1376.
NOTE: Bug 10509303 has been logged to address the documentation defect with how the file format is documented in the System Monitoring and Diagnostics Guide for Siebel Business Applications.
If the process id is known, then look at the second part of the file name to find the correct file, otherwise, use the timestamp in the first part as the guide. NOTE: If a crash_xxxx.txt file is available, convert the hexadecimal process id found in that file to a decimal value to identify the appropriate process id value that should appear in the .fdr output file name. The example below shows a crash.txt file generated in the Microsoft Windows environment.
NOTE: On HP-UX, the crash.txt file that is created in Siebel version 7.7 is a single file that gets appended. The process id is displayed in Decimal format as shown below:

How to Process Binary .fdr File into .csv Format and Identify the Crashing Thread

Here are the steps to follow to post process the raw .fdr file:
  1. Identify the appropriate .fdr file to process using process suggested above.

    NOTE: On UNIX platforms only, source the shell environment variables, before running the sarmanalyzer utility.
    To do this from the $SIEBEL_ROOT/siebsrvr directory, run the following shell command:

. ./

  1. Use the sarmanalyzer.exe command line utility and issue the following command:
sarmanalyzer -o <output_csv_file> -x -f <fdr_file>
For example:
sarmanalyzer -o T200503181601_P001376.csv -x -f T200503181601_P001376.fdr
The output .csv file will be written to the SIEBSRVR_ROOT\bin directory unless redirected to a different directory.
NOTE: While you can specific any file name for the .csv file, it is good practice to keep the same file name. This will maintain the date and time stamp as well as the crashing PID designations in the name of the file. This is useful when there are multiple FDR files generated and will provide reference points should these files need to be supplied to Technical Support.
  1. A best practice is to open the output .csv file using a spreadsheet application like Microsoft Excel so that you can easily filter the data.
    1. To do this in Excel you simply open the .csv file, use the Data menu item and select Filter > Auto Filter sub menu items.
    1. Next, to see the entries related to only the crashing thread, filter the SubAreaDesc column by the value ** CRASHING THREAD **.
    1. Select the ThreadID column and filter on the value (in this example, the value is 4068) that appears there for the record.
    1. And then unset the filter on the SubAreaDesc column. This should cause all records with the same thread id as the crashing thread to be displayed. These are the relevant records to review when analyzing FDR output. Please note that several threads may crash before the process is terminated by the operating system, in which case you may find several such FDR records.
    1. Please note that the .csv file created by sarmanalyzer.exe is not sorted. An important step is to sort the file in chronological order. For performance reasons, the FDR file does not contain timestamps. However, you can sort on the FdrID column in ascending order to rearrange the data in chronological order.

How to Flush FDR Output

Besides automatically creating the .fdr output file when a process crashes, it is possible to force the file to be flushed (written to disk) on command. The Siebel Server task id needs to be provided as an argument. The following information describes the steps to force the .fdr file to be flushed.
To cause the FDR buffer for a component process to be written to disk follow these steps:
  1. Identify the task you want to generate the dump for. This can be done by using the srvrmgr.exe command line utility and the list tasks command or navigating to the Administration – Server Management > Server > Tasks view from the Site Map in the Siebel application. For example:
srvrmgr> list tasks
    1. Identify the task id value for the component task that you want to generate the dump for and note it.
  1. Flush the FDR buffer to disk. Using the srvrmgr.exe command line utility and execute the command:
  srvrmgr> flush FDR for task <task_id> (for version 7.7. and 7.8)
  srvrmgr> flush FDR for process <process_id> (for version 8)
Where task_id in the statement is replaced with the value identified in step 1a.
    1. The FDR file will be written to the SIEBSRVR_ROOT\bin directory with the naming convention:
An example of this is:
This evaluates to an FDR file for process id 2576 where the process was started at approximately 1:23pm on March 12, 2004.
  1. Identify the correct OS thread id for your task. Within the FDR file, each entry includes the OS thread id related to the operation captured, not the task id. To find the relevant OS thread id used by the component task, use the following command on the srvrmgr.exe command line utility:
srvrmgr> list tasks show CC_ALIAS, TK_TASKID, TK_TID, TK_PID
This will generate a list of tasks and include the component alias (CC_ALIAS), the task id (TK_TASKID), the OS thread id (TK_TID), and OS process id (TK_PID).
Note the TK_TID and TK_PID values for the appropriate task id that you have flushed the FDR buffer for. This will help you find the appropriate FDR file described in 2a (the last part of the file name should map to the TK_PID value), and after decoding the file, will help you identify the entries relevant to the task id you are interested in. Each entry should have a ThreadID value equal to the TK_TID value. This is especially important when considering that a single process may have many threads.
 NOTE: ‘Bug 10632036 – FLUSH FDR COMMAND IS NOT GENERATING FDR FILES’ has been logged to address the defect, flush fdr for Siebel 8.1.1.x doesn’t work.
It is fixed in Siebel

How to Review Entries Prior to Crashing Thread to Understand What Happened Immediately Prior to the Crash

General structure of FDR entries includes the following columns:
The id assigned to a particular FDR entry. Each entry has a different id value.
The Operating System thread id. Each entry is associated with a thread, some entries may have the same or different thread id depending on whether the process is multi-threaded or not, and whether more than one thread is in use at the time of a crash.
Categorization for a particular subsystem so all entries can be grouped together.
Descriptive text of what product area each entry is associated with.
Similar to the area symbol, used to assign a unique categorization within a particular area for different functionality.
UserInt1, UserInt2
Integer values assigned by internal instrumentation that may store values like internal pointer references; this is normally only useful to Oracle Engineering.
UserStr1, UserStr2
These columns provide contextual information that is germane to understanding the significance of each entry and that may store object names, parameter values, row_ids or other messages that help indicate some context within the area and sub-area.
Example Case
A custom DLL has been developed that can be called when string transformations are necessary. The DLL is called from a business service that includes custom eScript code to pass a parameter to the DLL and receive the output from it. In a particular implementation, eScript code on the Account business component WriteRecord event calls a workflow process that uses the business service. The script passes the location value of the account to the workflow, the workflow process passes the value as a process property to the business service, and that value is in turn passed to the DLL for processing.
In this scenario the DLL is incorrectly implemented in a way that causes the DLL to exit unexpectedly, and this in turn will cause the OM process hosting the user session that invokes the DLL to crash. The FDR output can be examined to show what the user session was doing prior to the crash and what happened in the different internal subsystems the object manager, scripting, and the workflow manager to track down the point of failure to the workflow process and to the step that calls the DLL.
Diagram of Interaction between Elements Involved in Crash Scenario
Steps to cause the failure:
  1. Login to the Siebel application and navigate to the Account List View.
  1. Create a new Account with a location value of New York and step off the record to commit it.
  1. Because the DLL will fail when the location value is set to TT, set the location of the record to TT and step off the record to commit it.
  1. Step #3 will cause the Object Manager process to crash, and an FDR file will be written to disk at SIEBSRVR_ROOT/bin. The web client behavior will be to display an error indicating that the Server is busy, and the client will need to initiate a new session if they want to continue using the application.
  1. The .fdr file will need to be post-processed using the sarmanalyzer.exe utility to determine what happened before the crash.
Analysis of the FDR output:
See the section above called “How to process binary .fdr file into .csv format and identify the crashing thread” for details on how to post-process the binary .fdr file and get the .csv file into the proper order showing the records of the session relevant to the crash.
After sorting the content of the .csv file by the FdrID column, scroll down to the bottom of the list and work up to see the last few entries prior to the record showing the crashing thread. The entries prior to the last one show what happened prior to the crash.
The output will help to show things like:
  1. The SWE command executed in the client to navigate to the Account List View.
  1. The applet where the account record is written.
  1. The business component and script event that is executed.
  1. The different methods that are invoked by the BusComp_WriteRecord event and what script language is used.
  1. The call in the script to invoke a workflow, and its execution by the workflow subsystem.
  1. The invocation of the business service and method from within the workflow and by the object manager.
  1. The execution of the script methods in the Service_PreInvokeMethod event.
  1. The last successful operation is the GetProperty(WF_LOC) call in the AA business service so it can be deduced that the next call in the business service  SElib.dynamicLink(“revstr.dll”, “_BlockRev@4”, CDECL,myloc); – is the point of failure. In fact, when reviewing the DLL code, it can be determined that the point of failure occurs when the DLL receives a value of TT and the file object is never initialized prior to an attempt to write to it.
  1. Finally the crashing thread.
In this case, analyzing the FDR output quickly shows:
  • the interaction of several subsystems in the product,
  • helps deconstruct how each one is utilized prior to a crash, and
  • assists in pinpointing the last several operations prior to the failure.
Given this information it is possible to reconstruct what led to the failure, the likely cause, and the areas to focus diagnostic and recovery efforts.

Where to go for more information

To review additional information about troubleshooting application crashes please see the following references:
  • Document 477520.1 addresses how to troubleshoot Siebel Server Component crashes on UNIX.
  • Document 477511.1 addresses how to troubleshoot Siebel component crashes on Microsoft Windows.
Note that the information about FDR in this Technical Note applies to Siebel application versions 7.7, 7.8 and 8.0. As mentioned in Document 477520.1 and Document 477511.1, it is possible to generate FDR files when the application crashes in 7.5.3, however because the format is different and the content is less evolved, customers must submit these files for analysis to Technical Support. The format and process for analyzing FDR files on 7.5.3 are not planned to be documented in the future.

face wash

Posted: April 13, 2015 in Uncategorized


Prevent diabetes problems: Keep your kidneys healthy

On this page:

What are my kidneys and what do they do?
Print Section (PDF, 180 KB)*

Your kidneys are two bean-shaped organs, each about the size of a fist. They are located just below your rib cage, one on each side of your spine. Every day, your two kidneys filter about 120 to 150 quarts of blood to produce about 1 to 2 quarts of urine. Urine flows from your kidneys to your bladder through tubes called ureters. Your bladder stores urine until releasing it through urination.

Drawing of the urinary tract inside the outline of the upper half of a human body. The kidneys, ureters, and bladder are labeled.


How can diabetes affect my kidneys?
Print Section (PDF, 128 KB)*

Too much glucose,* also called sugar, in your blood from diabetes damages your kidneys’ filters. If the filters are damaged, a protein called albumin, which you need to stay healthy, leaks out of your blood and into your urine. Damaged kidneys do not do a good job of filtering wastes and extra fluid from your blood. The wastes and extra fluid build up in your blood and make you sick.

Diabetes is a leading cause of kidney disease. Diabetic kidney disease is the medical term for kidney disease caused by diabetes. Diabetic kidney disease affects both kidneys at the same time.

If kidney disease runs in your family, you are also at risk for kidney disease. Talk with your family members about their medical history and your doctor about having your kidney function tested.

*See the Pronunciation Guide for tips on how to say the words in bold type.


What are blood pressure and high blood pressure?
Print Section (PDF, 124 KB)*

Blood pressure is the force of blood flow inside your blood vessels. Blood pressure is written with two numbers separated by a slash. For example, a blood pressure result of 130/80 is said as “130 over 80.” The first number is the pressure in your blood vessels as your heart beats and pushes blood through your blood vessels. The second number is the pressure as your blood vessels relax between heartbeats.

High blood pressure forces your heart to work harder to pump blood. High blood pressure can strain your heart, damage your blood vessels, and increase your risk of heart attack, stroke, eye problems, and kidney problems.


How does high blood pressure affect my kidneys if I have diabetes?
Print Section (PDF, 238 KB)*

High blood pressure is the other leading cause of kidney disease in people with diabetes. High blood pressure also is a result of damage from kidney disease. If you have high blood pressure, your kidneys may already be damaged. Even a small rise in blood pressure can quickly make kidney disease worse.


What should my blood pressure be?
Print Section (PDF, 281 KB)*

Your blood pressure goal should either be below 140/80 or 140/90 depending on whether you have kidney disease and how severe it is. Discuss your personal goal with your doctor.

A male doctor taking the blood pressure of a female patient.

Many people with diabetes have high blood pressure. However, keeping your blood pressure at your goal will help prevent damage to your kidneys, heart, brain, blood vessels, and other parts of your body. Meal planning, medicines, and physical activity can help you reach your blood pressure goal.

Have your blood pressure checked at every health care visit. Ask your doctor if you need medicine to control your blood pressure. Medicine that helps control your blood pressure can slow progression of kidney disease.

Two types of blood pressure-lowering medicines, angiotensinconverting enzyme (ACE) inhibitors and angiotensin receptor blockers (ARBs), have been found to slow progression of kidney disease in people with diabetes.

Drawing of three pill bottles with two upright and one on its side.


What are the symptoms of diabetic kidney disease?
Print Section (PDF, 210 KB)*

In the early stages, diabetic kidney disease does not have any symptoms. Kidney disease happens so slowly that you may not feel sick at all for many years. You may not feel sick even when your kidneys do only half the job of healthy kidneys. Only your doctor can tell if you have kidney disease by checking the protein, or albumin, level in your urine at least once a year.

The first symptom of diabetic kidney disease is often swelling in parts of your body, such as your hands, face, feet, or ankles. Also, large amounts of protein in your urine may cause urine to look foamy. Once your kidney function starts to decrease, other symptoms may include

  • increased or decreased urination
  • feeling drowsy or tired
  • feeling itchy or numb
  • dry skin
  • headaches
  • weight loss
  • not feeling hungry
  • feeling sick to your stomach
  • vomiting
  • sleep problems
  • trouble staying focused
  • darkened skin
  • muscle cramps

Drawing of a distressed woman who is slightly bent over and clutching her stomach.
Kidney disease may cause you to feel sick to your stomach.


How can I find out if I have diabetic kidney disease?
Print Section (PDF, 133 KB)*

The following tests can tell you and your doctor if you have diabetic kidney disease:

  • Blood pressure test. Your doctor will use a blood pressure cuff to check your blood pressure. You should have this test done at every health care visit.
  • Albumin and creatinine measurement. Your doctor will ask you for a sample of your urine to look for albumin. A high level of albumin in your urine may mean you have kidney disease. The urine sample is sent to a lab for a test that looks at the amount of albumin compared with the amount of creatinine, a waste product also in your urine. A urine albumin-to-creatinine ratio test result above 30 is a warning sign of kidney disease. You should have this test at least once a year.
  • Estimated glomerular filtration rate (eGFR) test. Blood drawn at your doctor’s office and sent to a lab can be tested to measure how much blood your kidneys filter each minute. If your kidneys are not filtering enough blood, you may have kidney damage or kidney failure. You should have this test at least once a year. The test results show the following:
    • eGFR of 60 or above is in the normal range
    • eGFR below 60 may mean you have kidney disease
    • eGFR of 15 or below may mean you have kidney failure

If your blood and urine test results show evidence of kidney damage or disease, your doctor may suggest more tests to help find out whether you have other health problems causing the damage. Other tests can include blood and urine samples for additional lab tests and imaging tests, or pictures, of your kidneys. Your doctor also may need to perform a biopsy, in which a small piece of tissue is removed from your kidney to look at with a microscope.


What can I do if I have diabetic kidney disease?
Print Section (PDF, 229 KB)*

Once you have diabetic kidney disease, you can slow it down or stop it from getting worse by watching your blood glucose and blood pressure numbers closely to keep them under control.

If you have high blood pressure or protein in your urine, you can take an ACE inhibitor or ARB to control your blood pressure and reduce kidney damage. If you are pregnant, you should not take an ACE inhibitor or ARB.

See your doctor often. Have your urine and blood tested as your doctor advises to see how well your kidneys are working. You also may need to see a nephrologista doctor who specializes in kidney disease.

Drawing of a man sitting at a table and checking his blood pressure.


Eating, Diet, and Nutrition
Print Section (PDF, 138 KB)*

Your dietitian or doctor may suggest a special eating plan for you. You may have to avoid a diet high in protein, fat, sodium, and potassium.

  • Cut back on protein, especially animal products such as meat. Damaged kidneys may fail to remove protein waste products from your blood. Diets high in protein make your kidneys work harder and fail sooner.
  • Avoid a high-fat diet. High-fat diets are high in cholesterol. Cholesterol is a type of fat found in your body’s cells, blood, and many foods. Your body needs some cholesterol to work the right way. For example, your body uses cholesterol to make certain essential hormones and maintain nerve function. However, your body makes all the cholesterol it needs. If you often eat foods that are high in cholesterol, or if high cholesterol runs in your family, extra cholesterol in your blood can build up over time in the walls of your blood vessels and arteries. High blood cholesterol can lead to heart disease and stroke, some of the biggest health problems for people with diabetes.
  • Avoid high-sodium foods. Sodium is a mineral found in salt and other foods. High levels of sodium may raise your blood pressure. Some high-sodium foods include canned food, frozen dinners, and hot dogs. The amount of sodium is listed on the food label, so you can see which foods have the highest levels. Try to limit your sodium to less than a teaspoon a day, or about 2,300 milligrams (mg) a day. If you have high blood pressure or are African American, middle-aged, or older, aim for no more than 1,500 mg of sodium per day. Ask your doctor or your dietitian about how much sodium you can have.
  • Ask your doctor about the amount of potassium you need. Potassium is a mineral that helps your heartbeat stay regular and muscles work right. Healthy kidneys keep the right amount of potassium in your body. However, if you have severe kidney damage, high levels of potassium may cause an abnormal heart rhythm or even make your heart stop, called cardiac arrest. Some high-potassium foods include apricots, bananas, oranges, and potatoes.


How can x rays affect my kidneys?
Print Section (PDF, 124 KB)*

X rays that use a special dye—known as contrast medium—to give a better picture of your organs can pose a risk to your kidneys. Contrast medium that is injected into your blood vessels is the type that can cause kidney damage. If you need x rays with contrast medium injected into your blood vessels, your doctor can give you extra fluids and medicine before and after the x rays to protect your kidneys. Or, your doctor may decide to order a test that does not use contrast medium.


What is kidney failure?
Print Section (PDF, 124 KB)*

Kidney failure, also called end-stage kidney disease or ESRD, means your kidneys no longer work well enough to do their job. You will need treatment to replace the work your kidneys have stopped doing.


What happens if my kidneys fail?
Print Section (PDF, 303 KB)*

The two treatments for kidney failure are dialysis and a kidney transplant.


One way to treat kidney failure is with dialysis, which does some of the work your kidneys used to do.

One form of dialysis, called hemodialysis, uses a machine to circulate your blood through a filter outside your body. If you choose hemodialysis, you should watch how much liquid you drink. Your dietitian will help you figure out how much liquid to drink each day. Extra liquid can raise your blood pressure, make your heart work harder, and increase the stress of dialysis treatments. Remember that many foods—such as soup, ice cream, and fruits—contain water. Ask your dietitian for tips on controlling your thirst.

The other form of dialysis, called peritoneal dialysis, uses the lining of your abdomen, or the area between your chest and hips, to filter your blood inside your body.

You and your doctor will decide which type of dialysis will work best for you.

Drawing of a woman receiving hemodialysis treatment in a clinic. A wall clock behind the woman reads 10:10 a.m
Dialysis does some of the work your kidneys used to do.

Kidney Transplant

Another way to treat kidney failure is to have a kidney transplant. This operation gives you a healthy kidney from a donor.

A donor may be a living person. A living donor may be a blood relative, such as a parent, brother, sister, or child, or a close friend or nonblood relative, such as a spouse. A living kidney donation offers the best-quality kidney with the shortest wait time. Donating a kidney does not put the donor at risk for future health problems.

If you cannot get a kidney from a living donor, your name can be placed on the national waiting list for a deceased donor kidney, or a kidney that is taken from a person who has just died or suffered brain death. The wait for a deceased donor kidney is often longer than the wait for a living donor kidney.

Both living and deceased donor kidneys should be a good match for your body.


How does smoking affect my diabetes and kidneys?
Print Section (PDF, 197 KB)*

If you already have kidney disease, smoking can worsen any blood vessel, heart, and kidney problems. Kidney cancer is also more common in smokers.

Smoking and diabetes are a dangerous mix. Smoking raises your risk for many diabetes problems. If you quit smoking,

  • you will lower your risk for heart attack, stroke, nerve disease, kidney disease, and amputation, which is surgery to cut off a body part
  • your cholesterol and blood pressure levels might improve
  • your blood circulation will improve

If you smoke, stop smoking. Ask for help so that you don’t have to do it alone. You can start by calling 1–800–QUITNOW or 1–800–784–8669.

Drawing of a no-smoking symbol. A lit cigarette inside a circle is crossed out by a heavy line.


How can I keep my kidneys healthy?
Print Section (PDF, 255 KB)*

You can keep your kidneys healthy by taking these steps:

  • Keep your blood glucose numbers as close to your target as possible. Your doctor will work with you to set your target blood glucose numbers and teach you what to do if your numbers are too high or too low.
  • Keep your blood pressure numbers as close to your personal goal as possible. If you take blood pressure medicine, take it as your doctor advises.
  • Eat healthy meals and follow the meal plan that you and your doctor or dietitian have worked out. If you already have kidney disease, you may have to avoid a diet high in protein, fat, sodium, and potassium.
  • If you choose hemodialysis, watch how much liquid you drink. Your dietitian will help you figure out how much liquid to drink each day.
  • At least once a year, have these tests for kidney disease:
    • blood pressure test
    • albumin and creatinine measurement
    • eGFR
  • Have any other kidney tests your doctor thinks you need.
  • Avoid taking painkillers often. Daily use of nonsteroidal anti-inflammatory drugs, such as the arthritis-type painkillers ibuprofen and naproxen, can damage your kidneys. If you are dealing with chronic, or long lasting, pain from a health problem such as arthritis, work with your doctor to find a way to control your pain without putting your kidneys at risk.
  • See a doctor right away for bladder or kidney infections. You may have an infection if you have these symptoms:
    • pain or burning when you urinate
    • a frequent urge to urinate
    • urine that looks cloudy, reddish, or dark
    • fever or a shaky feeling
    • pain in your back or on your side below your ribs
  • If you smoke, stop smoking.

Drawing of a woman talking with her doctor.


Pronunciation Guide
Print Section (PDF, 127 KB)*

albumin (al-BYOO-min)

amputation (AM-pyoo-TAY-shuhn)

angiotensin (AN-jee-oh-TEN-sin)

cholesterol (koh-LESS-tur-ol)

circulation (SUR-kyoo-LAY-shuhn)

creatinine (kree-AT-ih-neen)

dialysis (dy-AL-ih-siss)

glucose (GLOO-kohss)

hemodialysis (HEE-moh-dy-AL-ih-siss)

inhibitors (in-HIB-ih-turs)

nephrologist (neh-FROL-uh-jist)

peritoneal (PAIR-ih-toh-NEE-uhl)

potassium (poh-TASS-ee-uhm)

sodium (SOH-dee-uhm)


For More Information
Print Section (PDF, 133 KB)*

To find diabetes educators (nurses, dietitians, pharmacists, and other health care providers), contact

American Association of Diabetes Educators
200 West Madison Street, Suite 800
Chicago, IL 60606
Phone: 1–800–338–3633
Internet: leaving site icon

To find dietitians, contact

Academy of Nutrition and Dietetics
120 South Riverside Plaza, Suite 2000
Chicago, IL 60606–6995
Internet: leaving site icon
Click on “Find a Registered Dietitian.”

To learn more about kidney problems from diabetes, contact

National Kidney and Urologic Diseases Information Clearinghouse
3 Information Way
Bethesda, MD 20892–3580
Phone: 1–800–891–5390
TTY: 1–866–569–1162
Fax: 703–738–4929

National Kidney Disease Education Program
3 Kidney Information Way
Bethesda, MD 20892
Phone: 1–866–4–KIDNEY (1–866–454–3639)
TTY: 1–866–569–1162
Fax: 301–402–8182

American Kidney Fund
11921 Rockville Pike, Suite 300
Rockville, MD 20852
Phone: 1–800–638–8299
Internet: leaving site icon

National Kidney Foundation
30 East 33rd Street
New York, NY 10016–5337
Phone: 1–800–622–9010 or 212–889–2210
Fax: 212–689–9261
Internet: leaving site icon

To get more information about taking care of diabetes, contact

National Diabetes Information Clearinghouse
1 Information Way
Bethesda, MD 20892–3560
Phone: 1–800–860–8747
TTY: 1–866–569–1162
Fax: 703–738–4929

National Diabetes Education Program
1 Diabetes Way
Bethesda, MD 20814–9692
Phone: 1–888–693–NDEP (1–888–693–6337)
TTY: 1–866–569–1162
Fax: 703–738–4929

American Diabetes Association
1701 North Beauregard Street
Alexandria, VA 22311
Phone: 1–800–DIABETES (1–800–342–2383)
Internet: leaving site icon

26 Broadway, 14th Floor
New York, NY 10004
Phone: 1–800–533–CURE (1–800–533–2873)
Fax: 212–785–9595
Internet: leaving site icon


More in the Series
Print Section (PDF, 299 KB)*

The Prevent Diabetes Problems Series includes seven booklets that can help you learn more about how to prevent diabetes problems:

For free single copies of these booklets, write, call, fax, or email the

National Diabetes Information Clearinghouse
1 Information Way
Bethesda, MD 20892–3560
Phone: 1–800–860–8747
TTY: 1–866–569–1162
Fax: 703–738–4929

These booklets are also available at

Image of booklets in the Prevent Diabetes Problems Series.


Print Section (PDF, 139 KB)*

Publications produced by the Clearinghouse are carefully reviewed by both NIDDK scientists and outside experts. The National Diabetes Information Clearinghouse (NDIC) thanks Katherine R. Tuttle, M.D., F.A.S.N., F.A.C.P., of the National Kidney Foundation, Providence Sacred Heart Medical Center, and the University of Washington, School of Medicine, for reviewing the updated version of this publication.

The NDIC also thanks the following people who helped review or field-test the original version of this publication:

For the American Association of Diabetes Educators
Lynn Grieger, R.D., C.D.E.
Arlington, VT
Celia Levesque, R.N., C.D.E.
Montgomery, AL
Teresa McMahon, Pharm.D., C.D.E.
Seattle, WA
Barbara Schreiner, R.N., M.N., C.D.E.
Galveston, TX

For the American Diabetes Association
Phyllis Barrier, M.S., R.D., C.D.E.
Alexandria, VA
Linda Haas, Ph.C., R.N., C.D.E.
Seattle, WA
Kathleen Mahoney, M.S.N., R.N., C.D.E.
Drexel Hill, PA
Randi Kington, M.S., R.N., C.S., C.D.E.
Hartford, CT

For the Centers for Medicare & Medicaid Services
Baltimore, MD
Jan Drass, R.N., C.D.E.

For the Diabetes Research Centers
Albert Einstein School of Medicine
Norwalk Hospital
Norwalk, CT
Jill Ely, R.N., C.D.E.
Sam Engel, M.D.
Pam Howard, A.P.R.N., C.D.E.

Indiana University School of Medicine
Indianapolis, IN
Madelyn Wheeler, M.S., R.D., F.A.D.A., C.D.E.

VA/JDF Diabetes Research Center
Vanderbilt School of Medicine
Nashville, TN
Ok Chon Allison, M.S.N., R.N.C.S., A.N.P., C.D.E.
Barbara Backer, B.S.
James W. Pichert, Ph.D.
Alvin Powers, M.D.
Melissa E. Schweikhart
Michael B. Smith
Kathleen Wolffe, R.N.

For the Grady Health System Diabetes Clinic
Atlanta, GA
Ernestine Baker, R.N., F.N.P., C.D.E.
Kris Ernst, R.N., C.D.E.
Margaret Fowke, R.D., L.D.
Kay Mann, R.N., C.D.E.

For the Indian Health Service
Albuquerque, NM
Ruth Bear, R.D., C.D.E.
Dorinda Bradley, R.N., C.D.E.
Terry Fisher, R.N.
Lorraine Valdez, R.N., C.D.E.

Red Lake, MN
Charmaine Branchaud, B.S.N., R.N., C.D.E.

For the Medlantic Research Center
Washington, D.C.
Resa Levetan, M.D.

For the Texas Diabetes Council
Texas Department of Health
Austin, TX
Luby Garza-Abijaoude, M.S., R.D., L.D.


National Diabetes Education Program

1 Diabetes Way
Bethesda, MD 20814–9692
Phone: 1–888–693–NDEP (1–888–693–6337)
TTY: 1–866–569–1162
Fax: 703–738–4929

The National Diabetes Education Program is a federally funded program sponsored by the U.S. Department of Health and Human Services’ National Institutes of Health and the Centers for Disease Control and Prevention and includes over 200 partners at the federal, state, and local levels, working together to reduce the morbidity and mortality associated with diabetes.

National Diabetes Information Clearinghouse

1 Information Way
Bethesda, MD 20892–3560
Phone: 1–800–860–8747
TTY: 1–866–569–1162
Fax: 703–738–4929

The National Diabetes Information Clearinghouse (NDIC) is a service of the National Institute of Diabetes and Digestive and Kidney Diseases (NIDDK). The NIDDK is part of the National Institutes of Health of the U.S. Department of Health and Human Services. Established in 1978, the Clearinghouse provides information about diabetes to people with diabetes and to their families, health care professionals, and the public. The NDIC answers inquiries, develops and distributes publications, and works closely with professional and patient organizations and Government agencies to coordinate resources about diabetes.

This publication is not copyrighted. The Clearinghouse encourages users of this publication to duplicate and distribute as many copies as desired.

This publication may contain information about medications and, when taken as prescribed, the conditions they treat. When prepared, this publication included the most current information available. For updates or for questions about any medications, contact the U.S. Food and Drug Administration toll-free at 1–888–INFO–FDA (1–888–463–6332) or visit Consult your health care provider for more information.

NIH Publication No. 14–4281
February 2014


Page last updated May 21, 2014

run task for comp GenTrig with EXEC=True,Remove=True,PrivUser=crminfo,PrivUserPass=”sabs@100″,ALERTLEVEL=2,ERRORFLAGS=1,TRACEFLAGS=1,SQLFLAGS=8